Nanoserver VHDx is not created with newer CU than 14393.2724
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- powershell
- Domain
- infrastructure, operating-systems
Research direction
Start by locating the NanoServer VHD creation path and the logic that selects MSUs or the latest cumulative update. Reproduce the behavior with a newer CU and with 14393.2724 (KB4480961), then determine whether the intended resolution is to change the selection logic or document the existing workaround.
Written by the indexing model from the issue text.
Description
Looks like by design as NanoServer is no longer supported anyway. If you need NanoServer VHD for some testing, skip MSUs or select 14393.2724 as latest (kb4480961)
- Dominant language
- PowerShell
- Stars
- 1.3k
- Forks
- 304
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/MSLab
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
oblt-aw/detector/security
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Type: AVM :a: :v: :m: Type: Bug :bug:
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/bicep-registry-modules#7386 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100