I had 19042.538 in a VM and rolled-back to 19042.508. It wasn't an issue. I've also rolled back from 19042 to 19041 because I'd like to have the option of being able to do an in-place upgrade when a final 19042 release is available. Even though I'm hearing 508 is final, I'm suspicious that there will be a release beyond 538.
Only if you didn't run a cleanup you have the uninstall option. Without the 20H2 EP it won't be 20H2, what gut feeling do you have based on what? I can't even find the words to respond. Oh wait: https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-208#post-1614775 How likely would it be that MSFT releases the 20H2 EP thru the slow ring first, next to the release preview ring and put it in the 19042.450 Techbench IP ISOs and now decides to remove it and recompile a new build, after declaring 19042.508 being the final and compile a new build with another method of enabling the 20H2 features what factually would become a major new release. seems i found some words...
Why would it not be necessary to respond to the utter bs you post there? Maybe it's not necessary to post every delusional thought that springs from your mind? We're not on social media.
guys, is there a way at the moment to upgrade to 20h2 without signing in on the insider program? thanks
Can someone tell me all the updates' locations? Disc cleanup often finds files related to updates (sometimes +1 GB) even when the Software Distribution and the LCU folders (the latter inside the servicing folder) are empty.
You're right about the EP. So I edited my original post about that. The EP was retained as we transitioned from 1903 to 1909, and will probably be retained as we transition from 2004 to 20H2. We have had two EPs already and I would prefer that we not have another one. Secondly, some functionality of 19042 is still broken, and I suspect that another CU might be in order for the final release. Enthousiast, I'm just a person that sits behind a PC like you do. Try not to be offended by gobbledygook that comes out of my mouth. It's not gonna harm you.
So it doesn't clean the folders I mentioned (I guess I can keep on cleaning their content since I'll be able to uninstall the updates if I want afterwards and I won't have other problems on WU)? Could you tell me why I shouldn't touch it (it's over 6 GB)? I never understood why are there files and folders with a date modified way before the Windows install, the difference between "Size" and "Size on disk" and why doesn't Windows remember window size and position sometimes, by the way.
To my knowledge, it clears both the directories and the SxS Store (in \Windows\WinSxS). Do not ever touch the Side-by-Side Store! The SxS Store contains all Windows system files and much more, what you see in Windows and System32 is only hard-linked from there. Simply deleting files from the SxS Store will corrupt or even kill the installation. It's all handled by Windows itself, Cleanmgr or Storage Senses can cleanup it in a safe way.
Thanks. I presume Windows grows on size because of that folder. Could you answer the other questions?
Once MS will press the red button. When exactly that will be is still up to speculation. (In other words, nobody knows.)
I've been away in the army and I haven't kept up with the Windows updates and bugs. Last I checked, there was a bug with windows update and disk cleanup. Has it been fixed yet? As a workaround I had to disable "servicing" or whatever it's called.