Windows 10: 1709 Fall Creators Update - System Thread Exception Not Handled

Tried a few times to install the 1709 creators update.

After configuring the update and restarting I get a
system thread exception not handled error.

In the end Windows restores the previous version.

Obviously it leaves me puzzling as to what might have caused the issue.

Will let it rest for a while.Probably the only way is to do a clean install (reset) which requires a lot of time on installing the applications...

Is there a way to do a kind of 'pre-scan-tool' that checks if everything is okay/1709 compatible or something?

Thanks.
=




:)

 

Windows 10 Update to Version 1709 fails with Stop Code "SYSTEM THREAD EXCEPTION NOT HANDLED"

I've seen this error reported several places on the internet but I cannot find a solution that works for this PC. I've tried updating from Windows Update option in Windows Settings and each time the error occurs during the second reboot of the update
process. The Windows update process completes to somewhere around 27 to 30% before the second reboot and fails during the reboot with the Stop Code "SYSTEM THREAD EXCEPTION NOT HANDLED". I also tried using the Windows Update Assistant location on Download Windows 10
but got the same result, except that the process fails during the first reboot due to the differences in the two processes. I then tried using the Windows MediaCreationTool to create a boot USB and then used it to boot the PC but when I run the Repair option,
no errors are found. I also ran the Windows Update Troubleshooter (https://support.microsoft.com/en-ph/help/4027322/windows-update-troubleshooter) and it reported that it "fixed" two errors but when I tried to update to 1709, I got the same error. So essentially,
I've tried all fixes I've found on the internet and still cannot update to version 1709. I've updated two other PCs to 1709, one of which was 2.5 years older (4/2009) than this PC (12/2011). What other options do I have to fix this problem? I clipped the
following from another site that reported this problem but the scenario is identical to mine. The person who reported this problem decided that his only option was to "install from scratch". I don't think that is a viable option because I probably would
have to do that with every Windows 10 update, currently about twice a year. Any help in resolving this issue would be greatly appreciated. Apparently, I'm not the only person experiencing this problem. Thanks! Name: Windows 10 - 1709 Fall Creators Update
- System Thread Exception Not Handled-31102017 071117.png Views: 1 Size: 877.2 KB ID: 161346" border="0" class="thumbnail" src="https://www.tenforums.com/attachmen...071117.png?s=e6818c0adf1e4251f5bcf1ade4a7b942"
title="Click image for larger version. Name: Windows 10 - 1709 Fall Creators Update - System Thread Exception Not Handled-31102017 071117.png Views: 1 Size: 877.2 KB ID: 161346" style="float:CONFIG">

 

Windows 10 Update 1709 install fails

I downloaded the Fall Creators' Update (No 1709). In Settings/Windows Update I get the message "This update is ready to install! We need your help deciding when to restart so we can finish." When I do a restart, the install will run for two or three restarts
and then I get a bluescreen with the message "Stopcode: System thread exception not handled" and Windows rolls back to the previous version, but the message requiring a restart reappears. How can I either fix this problem or skip this particular upgrade?

 

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is bugcheck 7e.
Run the DM log collector with English as the default language.
Then post a zip into the thread so that we can troubleshoot the logs:
BSOD - Posting Instructions - Windows 10 Forums
Language - Add, Remove, and Change in Windows 10 General Tips Tutorials

 

Note that it restored previous Windows setup, so there are no traces of any recent .dmp files/errors whatever.
OTOH again one or two new partitions. Only the 100MB can be deleted, the other two (471 and 458MB) - no delete option.

-

 

If you post the DM log collector we can troubleshoot the files.
Then if necessary the Panther files.

How do you like the HP dreamcolor?
Are you recalibrating it every 1000 hours?

 

Thanks. I'll think it over. Point is that I am not so much in favor of submitting a lot of more or less personal info on a forum, even though it may not be harmful and do not involve actual personal data. But, as said, I think it over. Another possibility I may consider is a reset, with a re-install of all applications.(which may be a better way?? instead of 'patching' and finding workaround)

As for the HP - it is a nice screen. Right now, I think, given its pricetag, there are some larger high quality screens around.
I should do a re-calibration some day. Haven't done it so far to be honest. Guess too lazy, or give priority to other matters, or likely .. both...



=

 

Hi,
How much space is used on C ?
How much free space is left on C ?
10 might not have enough room to create the windows old folder.
It's a efi / gpt disk so 10 can create more partitions as far as I can tell from the little disk management screen shot you posted.

 

For the DM log collector there is no personal information in the logs and to see what is collected you can view the threads in the bsod forum. It is msinfo32, dxdiag, event log etc. No pictures, or emails or personal files etc. The aim is to see what is abnormal.

For HP Dreamcolor I use it on a laptop and when you go beyond 1000 hours there are pop up reminders. Over time this is no joy as if you leave the computer on the 1000 hours occurs too quickly.

The failure to upgrade could be due to many factors and the more that is discerned from the logs the more likely you can figure out what needs to be fixed. After evaluating the basic computer logs for events, hardware, errors, additional logs can be viewed to further investigate the failure to upgrade.

 

@zbook - any suggestions as to how to postpone this 1709 update for a while?
I went into settings->Windows Update->Advanced Options and see an option

"Temporarily pause updates from being installed on this device for up to 35 days. When updates resume, this device willneed to get the latest updates before it can be paused again."

that can be set to 'Off'.
But maybe that is the wrong option/method?

Thanks
-

 

Thanks for commenting.I think space probably shouldn't be so much of a problem.
The small partitions have been created by Windows major updates in the past. They seem to be for recovery purposes.
One thing is for sure: I can not delete them within dskmgmt. I guess when doing a Windows install from scratch, I can, but not right now. Then again, they are small (2x roughly 400-500MB).

-



-

 

There have been many threads to delay or avoid updates.
Many have tried without success.


Enable or Disable Windows Update Automatic Updates in Windows 10 Windows Update Activation Tutorials
There are some options in this thread but the usefulness may have changed with each upgrade from 1511 > 1607 > 1703.
For example the metered connection use to work and some have commented that it no longer works.


There are many that want to upgrade and cannot.
It may be possible to find the problem they are experiencing and recreate it. However you are trading one problem for another.

 

Ah!
Thanks for the tip/thread.

I just want to avoid that Windows automatically installs the update at pc close, until I've my mind up when and how to proceed.
As said, likely I'll be doing an install from scratch (using USB, Media Creation tool, etc) but installing the applications and doing all the settings, well, it'll take a day or even more.
As for me.. it is not particularly a 'happy installing' job, so to say...

 

Ah!
Thanks for the tip/thread.

I just want to avoid that Windows automatically installs the update at pc close, until I've my mind up when and how to proceed.
As said, likely I'll be doing an install from scratch (using USB, Media Creation tool, etc) but installing the applications and doing all the settings, well, it'll take a day or even more.
As for me.. it is not particularly a 'happy installing' job, so to say...

 

I suffered for a long time from this dastardly problem. Every day Microsoft would assault me with aggressive "I'm gonna reboot" etc. And every morning I would start my day with a rebooted computer. Of course, the reason: the upgrade from 1703 to 1709 failed. So - WE DO IT AGAIN TODAY. Whoppee, Microsoft!!!!
Well, finally, my research gave me a clue. It's as if something is happening on a very low (like driver) level.
My solution:
I removed the following: BestCrypt Volume Encryption, LogMeIn and GoToMyPC. I had also added a Test Admin account based on another "solution".
I can't say for positive which of these simultaneous changes fixed it, but I am 85% sure it was BestCrypt.
My guess is that there are several causes for the failure.
Oh, and this: As I watched the update proceed and the reboots I saw this flash on the screen: "System Thread Exception Not Handled" (how helpful). However, a search on that led me to a "driver" thread. The idea being "bad drivers" were causing it.
That led me to look for yellow asterisks in Device Manager (found none).
But, as I said, my solution was to remove BestCrypt Volume Encryption.
Bottom line: Remove boot-level stuff.
What is "boot level stuff"? Anything that happens before you log into Windows.
The fact that LogMeIn and GoToMyPC allow you to boot into Safe Mode suggests that they do "boot level stuff". BestCrypt Volume Encryption forces you to enter a password way-before the Windows Login screen appears.
Remove all this stuff and you too may be able to stop hating Microsoft for a day or two.
One last comment: In defense of Microsoft. If you had 1,000 hackers trying to screw your o/s over, you too would have difficult challenges.
Regards