[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

You still HAVE NOT explained why there are 500 21H2 Files in 19043.1023 ? Saying it's nonsense is saying NOTHING.

 

You need to login to view this posts content.

 

Those files are placeholders, they are not active, there is no official announcement and at the end of the day it is Microsoft's design and they decide when it is ready or in preview or whatever else.

 

You're making it sound like he's the msft employee responsible for putting those files there. How about some common sense and remembering this is msft we're talking about.

 

This 21H2 is a useless vb_release build, not remotely related to "Sun Valley".
The legit Sun Valley will at the very least co_release, maybe co_refresh or cu_release.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

I agree. I find it doubtful that all the dormant features of 19044 are even present in the current build. Usually, the dormant features are added by LCUs prior to an EP that activates the dormant features. October or November 2021 is a long way off. If that is the actual release time for 21H2, then there is plenty of time to add more dormant packages. 21H2 could morph into something very different than we think it will be. It will be interesting to hear what MSFT has to say about it in their public announcement on June 24th.

 

I'm running 18363.1237 on my laptop and I want to install 19043.1023, but I don't want to:

- Upgrade.
- End up with boot files in the wrong partition (specifically D:\).
- Delete D:\ (I have a backup).

Which partitions should I remove during Windows setup? IIRC, it's only #3 that should be removed, but I'm not sure. It's been a while since I did it.

 

1. Please don't color text. Forum automatically switches between colors based on visual theme. In my case I'm reading black on gray - not fun.
2. What you want is a clean install - you boot into your install media, when you get to partitioning step you delete, in your case, 1 2 and 3, you select the newly "formed" unallocated space of ~301.3GB and you click Next. Just pay attention to partition sizes during partitioning step. That's how you tell which partition is which. Otherwise you could end up like me - yolo-removing your D partition and end up attempting file recovery. lol

 

Well, I didn't, but now I see the color being changed. Dunno why.

This won't make the install dependent of D:\ to be able to boot? That's what I remember from back in the days, but maybe Setup has gotten smarter over the years lol.
Thanks for your help.

 

you can delete all but the 630GB,
the best way to do this is to boot from the 19043.1023.

Your partitions are only incorrectly created because windows 1909 had an error in partition creation.

 

Ok, thanks. I didn't even know that there's anything wrong with the partitions.

 

You need to login to view this posts content.

 

Just wondering if this was addressed anywhere else, as I cannot find any relevant posts based on search on the forum.
The issue:
- Running 19043.985 upgraded in place with every single major version and some early pre-releases since ancient times, i.e. Windows 7. Did not go through Win8.x.
- In the CBS log I find entries related to old components which are more than likely orphans, but which I cannot find anywhere else than in this registry key where it appears following scans and sometimes disappears

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ApplicabilityEvaluationCache

The offending entries are:
Mapping_Package_for_KB3089226_af-ZA_amd64~31bf3856ad364e35~amd64~~10.0.10240.0
Package_for_KB3064238~31bf3856ad364e35~amd64~~10.0.1.2

I cannot find anything relevant under C:\Windows\WinSxS but they may be there hidden under different names.

Does anybody have any clue about what this means?

Apparently I cannot find the same entries on a clean installed 1904x, although this require further testing while trying to produce the issue.
Multiple people seem to report indirectly similar entries while publishing their cbs.log for other reasons.

sfc /scannow and dism /online /cleanup-image/<switches> do not show any errors

 

@ch100

Mostly are from Windows Update metadata leftovers

 

2021-06 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5003637)
Windows Malicious Software Removal Tool x64 - v5.90 (KB890830)
19043.1052

 

You need to login to view this posts content.