Re: Unable To Update Windows 10 1909 To 22h2
Mina Spartin
I have been stuck on Version 1909 since MAY, no updates at all since then. If I press CHECK UPDATES, nothing happens.. then I tried the update assistant. I have since tried it with ONLY MOUSE/KB USB, and Antivirus Disabled
each time it downloads, restarts, goes from 0% 8%, 30% and then restarts.. restarts.. till finally says CHANGING SETTINGS BACK and then sometimes restarts half a dozen more times till finally get back on Desktop and still on version 1909 no errors
I then tried Going to services.MSC and turning off and stopping WINDOWS UP, and BITS, then going to C:/windows/softwaredistribution and deleting files/folders
restarting and then trying to update and update assistant again.. same as before
ending up with me downloading the media creation tool. AGAIN ANTIVIRUS turned off.. I tired upgrading this pc and it downloaded files, restarted and did the same exact thing.. but this time gave me an error message
0xC1900101 - 0x30004
the installation failed in the FIRST_BOOT phase with an error during INSTALL_RECOVERY_ENVIRONMENT operation
I then tried booting into a USB that I created using the media creation tool.. I tried to UPGRADE but it would not let me do it.. said that I could not update from media startup or something and to restart the computer. only other option it gave me was to do a fresh install
I don't understand why, when it's going to install it almost instantly goes to 30% and just reboots. Am I going to have to totally re-install windows? I really don't want to?
but if I have too, it won't be that bad cause I installed a secondary m.2 last week and I cloned my C:/ drive onto it
I should also mention, the C:/ drive has 60GB remaining so it's not a space limitation. It's not a USB issue cause only KB/MOUSE is plugged in.. the antivirus is turned off.
I ended up fixing it.
I tried the ISO and it was giving me an error saying it couldn't continue to the next phase, but I thought about something.. WHY was it restarting constantly? even when running the update assistant it would get to 30% and restart.. so I went into the BIOS and set all setting to default... removed the XMP profile.. and then I ran the update assistant again.. this time it installed.. I'm guessing the XMP profile was messing with it somehow, maybe making something too hot and it would restart.
SO, now my original drive 960 EVO, I ended up removing that partition when trying to install the ISO, which lead to it saying my computer needed worked on.. LUCKILY I had cloned my drive to the new m.2 and the updated windows is now on that 2nd M.2 and my original drive is empty.. I still was unable to install a brand new copy on the 960 evo cause of the error message.. I think I know why. I didn't remove all other drives.. i'm guessing if I removed all drives and left only the 960 evo it would install.. but, as of right now I think i'll keep it like it is.. and possibly try installing windows 11 on the 960 evo.. if I don't like It, I can just swtich boot device to 2nd m.2 with the latest windows 10 update.
So, if you guys hear of someone else having an issue where it keeps restarting while trying to go through an update or install a new copy the way it was doing me.. make sure they reset bios settings to default settings. I'm just happy that I figured it out.. that is one thing about me, I have never let a computer problem defeat me LOL I'll troubleshoot for weeks at a time till I figure it out, or it drives me insane!
Disabling the XMP profile in my MSI bios appears to have fixed the problem for me as well. I have not been able to install a feature update past 1909 in over 2 years, it worked right away after the XMP profile disable.
After performing all of the above steps (post images into this thread using share links: one drive, drop box, or google drive) perform an in place upgrade repair in clean boot (make sure that all third party AV, firewall, and drive encryption are uninstalled).
And if i just install the KB, it said that i cannot install this kb on my laptop,however i choose the 64bits version as my pc so i don't know how can i install just the kb otherwise if it doesn't work with the Microsoft update catalog.
-EDIT- It's been a while since I did a feature upgrade via ISO download. You mount the ISO file and run setup.exe from there. I believe one of the options presented is to retain existing files and apps and that is what you want to select. After the upgrade to 22H2 completes, you might have to reinstall a few apps, one of them being possibly Eset. I would export your Eset existing settings, if modified, prior to Win 10 upgrade so they can be reapplied if Eset needs to be reinstalled.
According to this article: -management/upgrade-windows-10-eol-versions.html , you should be able to perform a feature update on a Win 10 EOL version via Win Updates. It is possible that is busted on your Win 10 installation.
I had the same issue on two of my computers that were on 1909. I was able to resolve it by using the media creation tool here: -us/software-download/windows10. Click the Download Now and do the upgrade (you don't actually have to create the media).
I do not know if it is related but a few months ago I randomly was prompted for the bit locker key when I turned on the system. I have no idea how or why this happened. I did not even know I had bitlocker up to that point. I can only assume it was something to do with the dell support assistant or the dell update app that caused it.
I have tried extensively to troubleshoot, tried DSIM, SFC and CHKDSK to check for corruption and errors, searched the internet for a solution and no matter what I have tried the windows 10 update 20H2 fails to install at 10% and undoes changes and stay at version 1909.
1. The "Intel Corporation - SCSIAdapter" refers to Intel's Rapid Storage Technology driver otherwise know as "RST". The version listed (17.9.6.1019), is the latest from Dell (released about a month ago), but it is not the latest from Intel. I would suggest that you download and install Intel's Driver and Support Assistant from here ( ) and see if it gives you a better one.
2. The second driver is the "STMicroelectronics Free Fall Data Protection driver". The version listed is 2.2.7.3. The latest version on the Dell Update site for your system is 4.10.105, A01 which appears to be way newer than your current version which leads me to wonder what Dell is doing here. How can the number jump so much? So you can try downloading and installing that.
NOTE: Before you do any updates it is highly recommended that you back up your entire system.. You can use the free version of Macrium Reflect to do this. Also create a Macrium "Rescue Media" in case your system has a serious problem.
You obviously have two driver issues. Check to see what devices these errors are referring to. Did you see if there are any updated drivers for these devices? If not, you might want to read through this post in the Windows Support Forum for a possible answer to one of the drivers.
The driver you have for Intel's RST is what is on the Dell update site. If not from Dell I am not sure where you might have gotten it except possibly through Windows Update which is not the best place to be getting driver updates.
Updated the STM driver (however I think I may have installed the wrong STM driver somehow as it wasn't being recognised in device manager before I attempted to update to window again. I went ahead with the windows update anyway and it showed up in device manager again after the update.)
(NOTE: To anyone reading this. Windows 10 version 1909 was no longer showing the 20H1 updates (it had already failed to install Windows 20H1 several times so I used the Windows 10 Update Assistant tool found online.)
Nice work. Glad I could help. You did a good job of finding what the update was complaining about. It would be nice of the updates would tell you directly what it does not like rather than you having to dig around to find it.
Intel's site strongly recommends for users to use their manufacturerer's version of RST because of customizations of the application. If Dell doesn't have one or it doesn't work, oh well. I'm taking Intel's advice over yours!
Following a factory reset, the device is at Windows 10 version 1903. The first run of Windows Update takes the unit (smoothly) to 1909. Then, on a subsequent check for updates, I'm offered 20H2. The initial stages complete correctly, all of the "Getting Things Ready" and (online) "Installing" sections run, and then the computer asks to be restarted. The unit restarts, and I get the blue fullscreen "Working on Updates / Don't turn off your PC, This will take a while / Your PC will restart several times." screen.
The screen proceeds to about 24%, and then does a reboot. The screen re-appears after that first reboot at about 30%, and, within just a minute, gives me the blue sadface "Your device ran into a problem and needs to restart" screen. It says:
8. I've looked for bootable ARM Windows 10 20H2 ISO images, but they do not exist (except, apparently, for Raspberry Pi, which seems off point for this. Microsoft offers recovery images for the ARM-based Surface Pro X, but I cannot locate any recovery images or other options for the Galaxy Book S).
So, rather than trying a rollback (which would have left me with the same PanelDriver.sys version) or an uninstall (which would have reinstalled the driver on the next boot), I moved the PanelDriver.sys file from the drivers folder to my Desktop, and rebooted. I then confirmed in Device Manager that the driver did not load and was missing. Without that driver all the hardware still seems to work fine, nothing was missing.
However, after moving the driver away, Windows offered me the 2020-12 Cumulative Update for Windows 10 Version 1909... and while that installed successfully, Windows Update is no longer offering me 2004 or 20H2.
d3342ee215