Forum Discussion
Unable to update Windows 10 Insider Preview 17063.1000 (rs_prerelease)
Hi,
This code refers to a possible driver issue, please refer to c:\windows\panther\setuperr.log & setupact.log to find out which driver is blocking your upgrade, if possible remove / update the driver / software for the upgrade
(if you get an access denied error on the logfile, just copy the files somewhere before opening them)
Hope this helps
Erik
I have the same problem. The latest version I made was 17025,1000. Since then, he has been trying for another five versions, but always unsuccessful. Lastly, it was version 17093. On disk C:\ I already have the seventeenth directory Windows.old (17). Directories can not be removed because the system reports that they do not exist. What should I do?
Deleted wrote:
I have the same problem. The latest version I made was 17025,1000. Since then, he has been trying for another five versions, but always unsuccessful. Lastly, it was version 17093. On disk C:\ I already have the seventeenth directory Windows.old (17). Directories can not be removed because the system reports that they do not exist. What should I do?
There are utilities you can use to remove some of those Windows.old directories. But you should keep the one that holds your last working production version of Windows -- you could theoretically fall back to that one if necessary, and apply updates later on when they are working for you, or when the next production release comes out. This might save the you hassle of doing a clean Windows install and reinstalling all your applications.
Be sure you know which directory you want to keep (especially the current Windows directory, as well as your last working production version of Windows). If you DO want to remove those directories, search the web for Iobit Unlocker. It's a free utility that will let you quickly unlock and, optionally, delete directories like this that appear impervious to deletion.
Re: compatibility: I think that part of the reason I finally get 17093 to install on my machine was that I used a 3rd party utility (I used Iobit's Driver Booster -- seems to be best to me, but there are others you can consider as well) to make sure all the drivers were completely up to date. That was one big change I made just prior to attempting the 17093 update. It's also possible that this build was simply more compatible and forgiving of surprises it might run into than prior builds had been -- I really don't know for sure if the driver updates made the difference.
