I did apply this EP on 19041.329 & now after the reboot, it's 20H1 19042.292? Any Idea why it is not 19042.330 & how to get it?
19041.330 needs the slow ring CU, to bump it to 19042.330 it needs the 20H2 Enablement Package. In your scenario you could now install the slow ring CU to 19042.330.
Weird small bug in 2004, ejecting a USB drive from the tray works fine. Same for just pulling it from the USB slot. However, if I eject the drive from Explorer by right clicking on its letter followed by Eject, you get a Disk event in Event Viewer log, such as: Might be another cosmetic disk management related bug, since ejecting it the other way doesn't generate the error. Obviously not a big deal, just a small curiosity, I was a bit worried at first because I assumed an SSD (which actually has the pagefile) is starting to fail, or that the USB passthrough on my new keyboard is defective. But, it was just the Explorer USB eject function. Also, I assume that the new Settings UI (with the account stuff on top, introduced in 2004) is not released for everyone? I am not having it on my PC on a clean install, it's the same as it was in 1909.
Not sure if this is the right place to post this, but just wanted to know if any of you have been experiencing the below behavior. Been noticing strange behavior after updating to 20H1. While running certain games, the GPU and system fans rev-up and the screen goes blank. Sound plays for sometime and after that, the only way to come out of it is via a hard rest. The system does not BSOD so there is no dump being generated, which makes it all the more difficult to find out the reason for the crash. I've also been noticing that DWM and Explorer.exe keep crashing often. I tried removing most Shell Extensions, SFC'd and DISM'd several times, and even re-installed Windows from the ISO generated by the latest MCT. Checked PSU output on the 12V rail and everything seems to be fine. GPU-Z also reports temps around the 70s, so I don't think it is a temp problem. I've even used the latest NVIDIA 451.22 dev driver but the issue persists. Was wondering if any of you guys also faced the same issue after updating? No such problem with 1909 so am thinking of rolling back for now. Specs: AMD Ryzen 9 3900X, 16GBx2 3600 CL16 GSKILL Trident. Gigabyte RTX 2080 Super, Aorus PCIe Gen4 SSD, MSI Prestige X570 Creation motherboard. All drivers, BIOS, and Windows patches up to date.
Getting this error when trying to install this windows10.0-kb4566866-x64_41af514390dc792f42e5ea586eb322b4f23263f2
i dont have and windows update says i am up to date. should i update it anyways. I don't have that and I am running the home edition. I would like to have that enabled but the last time I had it enabled it disabled itself within a few days but I forget how to enable it. It is not a big deal not having it though.
You need to mount the install.wim from your installation source and run... Code: Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess Adjust the path for the /Source switch accordingly. It's likely saying that your system is corrupt because you installed the 19042 enablement package before the CU, which removed old Edge and replaced it with Chromium Edge. If the cleanup won't fix it, and you don't have a backup to restore your system from, your only hope may be an in place upgrade.
I don't have any suggestions but will say that you are not alone with those symptoms. I've tried doing both fresh installs and in-place upgrades on a couple of machines with no video cards (Intel iGPUs) and have had the experiences requiring hard resets. I just finished reverting an upgraded machine back to 1909 again this morning. I wish they would blue screen and generate dumps.
Yes from the ISO you used to install if it matches your current CU. If it doesn't, you will need to acquire it. Copy the install.wim file someplace and mount it. Then run the cleanup command with /source switch pointing to wherever you mounted the wim.
will do that & update here. I did another test for this & this time, I did this in another fresh newly installed system where the latest 20H1 is installed, build 19041.329 Did not install the 20H2 EP first this time, but while trying to install this slow ring CU first, then also getting the same error like earlier here
For now I'm sticking with 19041. 'Not sure if this is the right forum for this, but kb4567523 was just released to Microsoft Catalog today (06/18/2020). That is 19041.331. Prior servicing stack kb4560366 released earlier this month is applicable. This is to fix print spooler issues. Just a heads up.