Upgrade error 0xC1900101-0×20017/0x30017 errors during upgrade from previous Windows versions to Windows 10. Try a log file analysis To find out, what causes this error code, try to analyze the log files created during setup. All log files are collected in hidden folders: $Windows.~BT\sources\Panther $Windows.~BT\sources\Rollback Folder Panther contains *.log files, whilst folder Rollback contains *.txt files. Just copy these *.log files via explorer to desktop and open it in Windows editor notepad. Then search for the error code. In some cases, some additional hints may be found. Troubleshooting Upgrade error 0xC1900101-0×20017 If a log file analysis doesn’t provide any clue about the root cause, you can process the following checks to prevent show stoppers: Convert your hard disk into a GPT partition scheme (only on UEFI systems) – see the remark from my MVP colleague Andre da Costa within for this US-Wiki. If you’ve use Truecrypt, encrypt your whole disk and try upgrade again. As mentioned in my old (German) Windows 8.1 blog post, remove unused 2nd hard disks. Here jwbecker mentioned, that SSDs connected to a RAID or other storage controller was the root cause. Plugging it to a SATA controller solved the issue. Also a storage controller O2Micro was found as a show stopper. Here is a hint, that this is a hardware specific issue affecting a few Samsung models which are expecting a specific IOCTL to be set on boot. There is no fix for such machines afaik. I’ve seen also reports, where Paragon’s Migrate OS to SSD 4.0 was supposed to be the root cause (see). Here somebody mentioned, that a disabled UEFI boot on a Samsung notebook was the cause. Disable netword and Wifi adapters (and use an ISO file created via Media Creation Tool) for upgrade. Here I found a suggestion to remove a Broadcom WiFi module. Here some guys have to upgrade the BIOS (to disable overclocking, see ASRock-forum). See also this MS Anwers thread. It seems that it hits also Intel Pentium G3258 – in this case, disabling one core could solve the issue. On some systems with Intel CPU, it seems that KB3064209 (an Intel Microcode update issued in June 2015) caused the issue. This update changes C:\Windows\system32\mcupdate_genuineintel.dl. See this MS Answers thread to get a workaround for this issue. Sometimes resetting the BIOS to optimized defaults worked. I’ve seen also incidents, where tools like IOBit driver booster or Tuning tools are the root cause for this update error. If the tips given above won’t fix the problem, refresh your previous Windows copy and try upgrade again. Also a clean install solved the problem (but there is the activation problem for Upgrade solutions) -------------------------------------- Troubleshooting Upgrade error 0xC1900101-0×20017/0xC1900101-0×30017 Microsoft supporters told me: This is a failure to boot into Windows 10 immediately after the WinRE phase. It’s typically due to a boot critical 3rd party driver. Unfortunately, there is nothing very actionable for those hitting this error. About all you can do externally is to make sure all your drivers are up to date, and remove any drivers not absolutely needed. Here a few hint’s what I’ve observed in German MS Anwers forum as show stoppers: Uninstall your security software (firewall, antivirus software, protect software) and try to run also a clean tool provided by software vendor (to clean remaining filter drivers). Uninstall TuneUp, virtual drive software and similar tools – undo all “changes” made by tuning tools. Remove all unused devices and deactivate drivers/devices in device manager. Some users are reporting non compatible graphics driver causing this error message. If possible, uninstall your graphic adapter driver and try VGA driver during upgrade. Also take care, that the disks are not encrypted (TrueCrypt) and also in proper NTFS-MBR/GPT-Format.
"Let apps run in the background" in privacy settings is broke in this rtm release. after setting it to off, its automatically going in on mode after restart. WTH.
I have these: 17134.1.180410-1804.rs4_release_clientbusiness_vol_x64fre_en-us_3322A5ADE9E29F74A61FD750614A939239780FEE.esd 17134.1.180410-1804.rs4_release_clientconsumer_ret_x64fre_en-us_E698E1F0C2E6022982A48E299E06936F84D83A74.esd Both of them have Windows Education. Is there a difference between Win Education from Client Business or Client Consumer ESD?
is it on MSDN yet? Stupid MCT image has install.esd...I need install.wim and I don't feel like dicking around with command line code to turn it into .wim Any link/help would be greatly appreciated.
Yeah, that's what I thought at first. Perhaps some failing hardware could be causing this issue and did run mem test, tested hardware, etc. System tested fine. As for hard drives, as stated, the only drive I have connected to the system when installing windows is the boot SSD drive... and that tested fine, SMART shows no concerns. Unfortunately though, Asus is no longer supporting the Rampage III. I have the latest firmware flashed several years ago in order to support hard drives greater than 4TB. So firmware update is not possible. I guess I'll try disabling one of the GPUs after work and give it one more try but I think the problem is something Microsoft is not supporting now or is handling differently than past version of Windows 10. Also... It's not that I'm not able to get a clean install of Windows 1803 installation files on the SSD. I was able to boot with 1709 ISO from Bluray Disc, remove old partition and create new one.... and then run 1803 setup (on USB drive) from the command prompt. Installation went fine as far as copying installation files across to the SSD. The problem is when the system reboots to continue installation, the installation process is again, stuck at the Windows Logo; same as stated above. So something Microsoft is doing in the April Update setup that is causing installation to freeze. As for overclocking, that's the first thing I thought could be the cause and have the system at stock speeds.. so I don't know what else there is to try myself. I've gone back and reinstall a fresh install of 1709... everything is working fine as before attempting 1803 installation. @nmook Yeah, that's pretty much the first thing I found when googling the error message... Those articles are talking about earlier problems with Win10, like Redstone 1 & 2.
no problem. i uninstalled all apps with power shell except few which can not be uninstalled. and i use startisback++ and it have option to block prelaunch of searchui and apps. now search and edge are not prelaunching.
hi guys i use these script in previous version of windows to delete things from windows update but on these 1803 not working any solution how fix it to be working ?? CD\ CD %Windir% CD SoftwareDistribution DEL /F /S /Q Download
Hello, some help please I just updated my 1709 x64 business to 17134.1 using esd>iso>setup.exe After several restarting it came to login screen. I logged in and the full screen blue message said "HI WE'VE GOT SOME UPDATES FOR YOUR PC" and it goes to "All done" Then strangely I got a black empty desktop with an error saying "C:\windows\system32\config\systemprofile\desktop is unavailable" when I press OK I get an empty desktop with a recycle bin that errors me with "explorer.exe an attempt was made to reference a token that does not exist" when I click it. My computer and my documents doesn't show up. Also networking, sound, settings app and start menu don't work, among other things. Tried sfc and dism scan health and restore health but didn't help. The same messages after every restart and logging in, starting with "Hi we got some updates..." and then black desktop Please help
your user profile is damaged, try to create a new user & login it from cmd as admin net user manolito /add net localgroup administrators manolito /add where manolito is your new user desired name & administrators must be in your own languaje close your actual sesion & login new user saludos from sapin
only migrate from old damaged home to new home very near the first one then from this new home you can try to repair the damaged home (search regedit profilelist),,,,, thanks