Does anyone know what to clean up after an upgrade attempt from Win 8.1 Pro w/MC x64 to Win 10 Pro failed (posted separately about that)??
The reason I ask is when I tried it a second time it didn't get past the 1st reboot before sending me back to my old OS. That usually indicates a cleanup is needed.
The installer the first time around told me everything was fine, except I'd lose WMC. But I got a flashing logon screen which refused to work and eventually locked up. I used Safe Mode Advanced Recovery in that instance.
Run Disk cleanup, then click cleanup system files, from the drive properties in File explorer. This will clean up most remnants.
Windows.old Folder - Delete in Windows 10 - Windows 10 blog
As simple as that ? Good !! Thanks. It'll be in Win 8.1 but same difference as they say.
There may be other files that may be deleted in the usual way - if there's still odd stuff, get back to me here.
That seems to have taken care of everything, thanks. Now whether or not another attempt at upgrading will work, is another matter LOL.
Hi Peter. Seems funny to see you here instead of in the vistax64 forum doling out Vista ISOs
Did you use the MS MediaCreationTool to download and create an ISO to use for the upgrade or did you do it via the Get Windows 10 icon or Windows Update?
I'd recommend downloading the iso then create a flash drive to install from or do as I did and just mount the ISO from Windows 8.1 and run setup.exe there. My first attempt failed at the shop so I cleaned up like you did then did the ISO create, mount and up-grade via setup.exe and it went perfect this time.
Hi,
I'm still doling those out like always. I used MCT for the upgrade from Win 8.1 Pro and once I had removed things like Start 8, Aeroglass hack from MSFN and my A/V all went smoothly. I learned quickly not to accept their recommendations and used custom settings.
The other system, my spare Win 7 Ultimate SP1 I have since upgraded using the ISO burned to a DVD. The tool failed "something happened" no matter what I did that I found by Googling that error. It went without a hitch.
I must say it's a blessed relief to be shot of Product Keys.