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
Hello to you, I was/am using BestCrypt as well (Container Encryption). However, in my case, it is almost certain it wasn't BestCrypt.
Now please check if Windows has been installed on DISK 0 (zero).
Run Diskmanagement : Win-R diskmgmt.msc
The first disk is DISK 0
Is Windows installed on that disk (0) ?
Maybe it is installed on DISK 1
In my case it was installed on DISK 1
After many, many ... failures, I decided to disable DISK 0 (in BIOS)
Then, automatically, the Windows disk (SSD) became DISK 0 (was DISK 1)
From that point on, installation went fine.
After installation of 1709, enable the drive again, in BIOS.
IF/IF this is the case with you, then pls check out:
1709 Fails to install and how to remove multiple recovery partitions?
Thank you for trying to help me.
Let me clarify:
1. My problem is fixed.
2. My (likely) culprit was BCVE.
Note: I was using BestCrypt VOLUME Encryption (BCVE). You are using BestCrypt CONTAINER Encryption (BCCE). These are very different. BCVE encrypts Windows. BCCE does not. BCVE requires a password before Windows boots.
As stated in my prior post, I removed BCVE, GoToMyPC, and LogMeIn simultaneously, so I’m not positive BCVE was the culprit (but I think so).
Sorry if my post was unclear. I am assuming that you thought I still had a problem.
Quote