Forum Discussion
Windows 10 Insider Preview 17666.1000 - failed install attempt - 0xc1900101
LS, it seems that the latest preview build does not get installed.
What's even more mysterious, is that the previous, successful installation, was a newer release than the one not installing currently - see below
54 Replies
I am stuck on build 17661 and have been for 6 months - 6 attempts to update with later builds all failed repeatedly. Seems to me that something in build 17661 is causing the issue. Msoft get a grip or you will lose many insiders as we get little assistance from you
- I had similar issues with that build but on about the third or fourth attempt it worked. I suspect there is now some form of adaptive code in there that changes to install depending on issues it encounters. It would be useful to know if that suspicion is a fact as it would save troubleshooting time... Since then all subsequent builds have installed smoothly.
has any of these issues been resolved with build 17682?
Probably like for most of you, Build 17666 is the first build that failed to install for me since I'm on Win10x64.
Build 17682 now installed successfully but it did not solve all the problems that came with this failed install. I did not do anything special to solve the problem besides giving each new build that came out after 66 a chance.
As it worked now, it seems the problems lies within the build itself (maybe some compatibility problem with our systems).
Maybe you guys have a Dell Studio XPS from 10 years ago like I do? This might be the common link between all of us but just a wild guess. Maybe it's the Radeon 3800 graphic card. Maybe it's the Samsung monitor that I'm using in portrait mode.
Build 66 failed to install and rolled back but still broke two things:
- My (Dell) ATI Radeon HD 3800 driver stopped working (error 39) and despite all attempts is still not working.
- My internal USB3 controler (Renesas - was not provided by Dell) seemed to be working but attaching USB3 Disks did not do anything (no lights, no motor turning).
I "solved" 1/ with buying a Geforce GT 1030 (glad that PCI-E ports are backwards compatible - even though it's not going to run full speed which is why I bought this entry level card) and replacing the Radeon. I always liked Geforce more anyway but it's a shame I had to come to that end. I don't know if the card just broke at the same time or what (the default Windows driver was working OK) but I was tired of losing time with this and wanted to upgrade the graphic card for a while anyway.
I solved 2/ by moving the internal controller to a different slot. Not sure why this changed anything but it's working as it's meant to.
Thanks to all for your support and suggestions and I you all now made it successfully to build 17682.
Have fun!
yes- after 2 fails I uninstalled Kaspersky and 17682.1000 installed on the third attempt with no issues and at lightning speed.
Yes, see comments. But If you install now Kaspersky. You have a boot loop and it's impossible to go to the previous version of windows. You need to reinstall completely windows...
Yes it does!
Had the same issue. Solved it.
1. Boot to safe mode
2. Nav to C:\Windows\SoftwareDistribution\Download
3. Delete the files
4. reboot to normal mode and install
5.???
6. profit
Thank you! That stopped that issue.
But now no programs works at all. I get message saying it couldn't run the program correctly because of error (0xc0000005).
Chrome was the only none windows 10 program that worked but the tabs was only going half the window which was weird.
Since these issues made my computer practically unusable I had to roll back to stable version.
did the same, due to the state of the build. After the rollback everything seems to behave and perform as one /I would expect and the OS is running build 17661.1001.
And I did pause the updating process for a few - want to wait and see what the community is sharing and Microsoft is doing about the build currently pushed.
what's that you are trying to emphasize at point 5?
Andor Oudt wrote:what's that you are trying to emphasize at point 5?
it's an internet joke. nm. ha.
17672.1000 doesn't work for me
- idem for me. It works if I uninstall Kaspersky Internet security before the update.
If I reinstall KIS with the 17672, I have a boot loop....
I have 2 choices...continue with windows 16672 and windows defender without KIS
or continue with windows 1803 with KasperskyI do not have Kaspersky Internet security but I do have Avast Antivitus.
Maybe it has something to do with conflicting with windows defender?
unfortunately, the latest update failed again ... rolling back to the 'previous' build.
Sideaffect was, that one of the apps doesn't start anymore (OneNote)
that is still 17666.. see if you can install 17672
currently downloading … thanks for pointing that out
How so? Failed update for me too, rolled back to my previous version on its own
I had a failed update twice with an error code, now the Status says installing, it gets up to 100% and then starts over at 0%. The status changes to "installing" back to "preparing to install", just constantly cycling.
The screen flickers constantly as Explorer seems to be stopping and restarting.
There was a antivirus update that is finally done so some progress is being made. Hopefully this next round gets finally complete.
I was running into this on my Surface Pro 4. Disconnecting the Surface Dock before restarting seemed to fix it for me.
I have the same issue.
So far there have been 4 failed attempts on getting the update.
I did use the bat file method mentioned earlier in this thread but it didn't do any difference for me.
I'm rn going to see if after using the troubleshooter it would work.Anyone managed to figure out any other alternative solution if it still doesn't work?
Build 17672 is out today.Downloading now.
Hope it installs!!
Please tell me how it goes! Will install as soon as I hear if it works or not
I am having the same issues. Are you on build 1803.
I was able to get mine to update by leaving it over the weekend.
PS: the install from stable to this insider preview took 2 hours, I was not expecting it to take that long.
No luck so far - the .bat file method failed, have tried the troubleshooter now 4 times with no success.
I hope this is a no issue with the next update, hopefully sometime next week.
Rip.
Yeah let's hope so!
- How 17661 can be called newer than 17666? You read the digit carefully.
- You are absolutely right sir, thank you for clearing that up
Has been fixed by resetting the Windows Update.
It's an old solution, helped me a lot of times.
- Create a bat file.
- Edit with notepad or something else.
- Paste this:
@ECHO OFF
echo Simple Script to Reset / Clear Windows Update
echo.
PAUSE
echo.
attrib -h -r -s %windir%\system32\catroot2
attrib -h -r -s %windir%\system32\catroot2\*.*
net stop wuauserv
net stop CryptSvc
net stop BITS
ren %windir%\system32\catroot2 catroot2.old
ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren "%ALLUSERSPROFILE%\application data\Microsoft\Network\downloader" downloader.old
net Start BITS
net start CryptSvc
net start wuauserv
echo.
echo Task completed successfully...
echo.
PAUSE- Save
- Run as administrator.
As you can see from the code, it just stops WU services, renames related directories and runs the services again.
Hope it will help.
