Main Forum > Everything Else
Windows 10 upgrade, 10 tries, 10 fails
GussNemo:
I have now tried to upgrade from Windows 7 Ultimate, 32 bit, to Windows 10 ten times and experienced ten failures. Each time the error messages are the same, for both the blue screen and on the Windows Update window.
On the blue screen I see "The PC has experienced a problem, please wait we are collecting information: System Thread Exception Not Handled." Collecting information? Whose collecting information? And where's it going? I'd like to see that information. (a few sarcastic questions I have)
The error message on the Windows Update page is as follows: Windows update experienced an unknown error, c1900101-30018.
As I normally do when I encounter a problem, I surf the web looking for solutions for the specific information I have. Namely the two error messages above. And I must say it is quite heart felt to see all the definitive solutions to my problem, as long I go along with the poster who said, "that didn't work for me." And let me apologize now for any sarcastic statements I will no doubt make. Nothing I'm about to relate has fix the UNKNOWN problem which Windows Update is encountering.
I did say I search for solutions when encountering problems, and I did that the first time the upgrade failed. One post said to run "chkdsk" and "sfc /scannow" which I did. No problems were found. One post said to go into Windows -> Software distribution -> Download and delete the contents. Which I did, still no help. I even ran several suggested Microsoft Fixit and Troubling shooting programs. Again, nothing fix the UNKNOWN error.
I've tried tweak after tweak but nothing cured the UNKNOWN error problem. As a side thought, while doing all this, I decided I better backup my hard drive only to find "Backup and Restore" were no longer working; I also had to buy a larger portable external drive to hold my HD contents--bought a Seagate 2TB portable expansion external drive. So, now I had another problem to research and try to find an answer. The possible answer can in a post which suggested running MiniToolKit, which I did. After running the program I noticed the system was running rather sluggish, and decided to reboot. Once the task bar appeared I noticed an icon on the Action Center icon which I hadn't seen before. Imagine my surprise after opening the Action Center to find my system was being backed up. That was one thing fixed, I think.
On to more posts, another suggesting Windows Updater--I believe it was called, which installed a program HotFix (I think). Anyway, this didn't fix anything either. Emeisoft Emergency Kit was suggested in another post, which I tried. It's a maleware program which ended up finding three PUPs which weren't hurting anything but I got rid of them anyway. More posts, more suggestions, none of which were use to me or I'd already tried.
Then another post caught my eye for Tweaking.com Window Repair, something I hadn't tried. Ran it, followed the directions, the program found some problems, let it fix those problems, thought now my system could be upgraded to Windows 10, ran the upgrade, and received the same to error messages I mentioned at the beginning of this post. Sooo...before the 10th attempt at upgrading to Windows 10, and something I did several times before, I disabled both Avast and Malwarebytes, Windows Defender, and Windows Firewall. I also disconnected the printer, USB 2.0 hub, the new drive I bought, and started the upgrade. And for the 10th time windows upgrade failed. It is nice, I must say, after each fail my system was restored to it's chipper self. Thank goodness.
Needless to say I'm at a loss what to do to find this UNKNOWN error. Trying this or that hasn't worked, so more of the same isn't a solution. Somewhere, someone must have the information which was gathered when the blue screen appeared. Information which might tell what the error is and maybe provide a clue how to fix it. Unless someone has any more ideas how to sleuth out this UNKNOWN error, it looks like I'm living with Windows 7 Ultimate 32 bit.
Boggin:
How have you been trying to upgrade ?
If it's through Window Update then that could have its own problems, have you tried it from https://www.microsoft.com/en-gb/windows/windows-10-upgrade
When upgrading you should have all peripherals disconnected.
I'm not sure what else to suggest for the Win 10 upgrade failure as you have probably tried them all and you will also have seen what a common problem it is, although you haven't mentioned using the System Update Readiness Tool (SURT).
http://windows.microsoft.com/en-gb/windows7/what-is-the-system-update-readiness-tool
You can find its log in C:\Windows\Logs\CBS\Checksur and double clicking on it will open it in Notepad.
Was that just a standard blue error screen or a BSOD ?
Did you run the Pre-Scan in Option 2 of the Windows Repair program to see if there were any corrupt Packages etc.
If push comes to shove then you could contact MS but they can leave the computer more in a mess than when they first started - depends upon the quality of tech that you get as they have some right dicks.
GussNemo:
Hi Boggin,
Yes, I've been trying to upgrade from Windows 7 Ultimate, 32 bit, to Windows 10. Ten tries and ten fails, all through Windows 7 update windows.
No, I haven't tried updating through any MS web page, specifically the one you provided; that might be something to try. I've also given consideration to going the ISO route, but worry if something goes foul, will it revert back to my previous version of windows.
Yes, I have installed the System Update Readiness Tool. But I don't know if it helped.
Windows 10 upgrade installation gets to 30% of installation and 100% of copy files, restarts the computer, then proceeds to installing features and drivers. At 32% of total installation and 6% or installing features and drivers, the "oops we have a problem" blue screen appears. That screen tells me my computer has a problem and they are gathering information. Who they are I haven't a clue--MS I'd guess. What information that's being gathered, again, I haven't a clue--probably information which would tell me what problem is being encountered.
When this blue screen appears, and the message I mentioned above, there is an error message right below the first one which says, "System Thread Exception Not Handled." According to MS, a clean boot should be preformed. And of course, this is something I've already tried--about 3 or 4 upgrade tries ago.
The Checksur log finds 4 corrupt errors dealing with IE. I have no idea if these would interfere with the upgrade or not.
When I ran the Windows Repair program I followed all the tabs at the top of the screen, except for Pro since I have the free version. According to the program, 43 problems were found and 43 problems were resolved.
Yeah, I'm not real thrilled with letting MS or another service dealer get into my computer system. From everything I've read, the problem I'm facing is not specifically known. Every possible fix is a "try this, if that doesn't work, try that" and that's no way to troubleshoot any complicated system. Someone, somewhere, should, after all the time Windows 10 has been available, been able to come up with a detailed troubleshooting flow diagram which can walk, walk, the user through fixing the problems they are encountering. [step off my soap box now]
I'll keep digging and see if someone hasn't found a fix from sometime this year, 2016.
Boggin:
If the ISO route also fails then it will auto roll back to your previous OS but prior to upgrading, succeed or fail, it's prudent to create a full system image of your current system onto external media.
As MS recommend a clean boot, I'm not sure if the upgrade can be done in Safe Mode with Networking using the MS webpage if the upgrade using that route also fails in normal mode, but it's something else to try.
I don't think MS use IE for Windows Updates any more but see if resetting IE to defaults resolves the errors Checksur reports.
You could also use the cmds in Method #4 in https://support.microsoft.com/en-us/kb/813444 to re-register IE as the faults SURT found could be relevant.
However, the list of .dlls the MS page gives to re-register is a lot shorter than what I've normally seen, such as in this 2013 article - http://downloadsnfix.blogspot.co.uk/2013/06/how-to-re-register-dll-files-of.html but create a restore point first.
As you've exhausted Google on that error, then I won't waste my time just to come up with the same suggestions you have already tried to no avail.
GussNemo:
Hi Boggin,
I'm keeping the ISO upgrade route on the back burner for now, there are a few other things I want to check before trying another upgrade. Three or four upgrade attempts ago, I did want to back up my HD only to find "Backup and Restore" not working; I also needed a larger external drive, which I now have. I ran a program called MiniToolKit and after it ran "Backup and Restore" was once again working--the system was making a backup all on its own, thank goodness.
I have tried doing a clean boot but that didn't cure the one error message on the blue screen page, System Thread Exception Not Handled. But according to MS a clean boot should have solved the problem. Should have, my personal comments will remain mine.
I will try resetting IE to all defaults, though I had a heck of a time once before getting all the "I don't want it" from running. Shouldn't things always use the KISS principle? I will also try to re-register IE as you've suggested, heck it just might be the one reason why upgrading fails. KISS, remember KISS.
I've been very tempted to leave a post on the MS community, but too many MS replies have been canned replies which didn't help the original poster. And many of the things those canned replies suggested I've already tried.
On the MS error list, for the error codes I'm seeing, it is suggested to reformat the HD from NTFS to GPT. Why? How is this going to fix anything when other machines running the NTFS format upgrade without this step being taken. Besides, I just want to upgrade the OS, not completely reinstall everything after formatting the HD. KISS, remember KISS.
I'll keep plugging along, maybe I'll get lucky and a magical fix will appear by accident.
Navigation
[0] Message Index
[#] Next page
Go to full version