System freezing after updating to Creator's build

[Saltgrass]

I am a little surprised no one has recommended booting the system with the Minimum configuration. Using a diagnostic startup can be helpful.

Since it froze after a clean install, that means Nero is not involved or did 1607 remove the problem encountered with 1703? Did the update which failed to install before ever install after the clean install or rollback?

When I start having problems with a system, I will leave Task Manger or the Resource Monitor open so I can keep an eye on what the performance parameters are doing. Along with that and keeping close track of what the system is doing, may help narrow down the problem. If the freezes happen when the system is idle, it may be some background process such as a virus scan or updates. If the system were trying to install a device driver, that might be the cause of the problems. If you are online, it might be a network driver. I will have to go back in the thread to find that number to see what it might be for.

 

[Data]

Well apparently Microsoft is recommending people dont upgrade to 1703 manually and bypass any blocks that were put in place to prevent some machines from running into problems.

Unless of course you are willing to work through the issues you find.

 

[Saltgrass]

The update which keeps failing is from 2015. I wonder why that update is trying to install now, after the Creator's update.

I have a sense, but cannot prove it, that with every large update, Windows is moving beyond certain types of devices and software. So each update may have a new series of problems, depending on what type of system and software you are running.

So far, all 5 of my systems are updating fine but none are more than 5 years old.

 

[clifford_cooley]

Since it froze after a clean install, that means Nero is not involved or did 1607 remove the problem encountered with 1703?

I have disappointing news since updating to 1607. A build of which I never had problems before 1703. I a now getting freezes after an update to 1607 from 1511. I didn't say anything after the first hoping it was a fluke. No luck had my second freeze this morning.

Did the update which failed to install before ever install after the clean install or rollback?

The update that never installs does stay after clean installs. It has been a long time but I specifically remember clean installing to get rid of it. Since then I haven't worried about it.

 

[Data]

Skip 1511 and install the 1607 from fresh. Dont give Windows Updates opportunity to screw things up.

 

[clifford_cooley]

There has to be something on my system causing all this. Now I just need to find it.

 

[Data]

Logs must tell something, you probably need to enable debug/verbose logging to see it.

 

[clifford_cooley]

Skip 1511 and install the 1607 from fresh. Dont give Windows Updates opportunity to screw things up.

Do you think that may help? I will try it. I was planning on doing that anyway last night until 1607 showed in Windows Updates.

 

[Data]

Its worth trying, but in any case if something is causing it (like software), there must be some log entry somewhere that gives some clew and you may need to enable verbose/debug logging in order to hunt it down should that 1607 install prove to not help your case.

But also upgrade 1607 to last available update.

 

[clifford_cooley]

Its worth trying

I haven't tried yet. Instead I took thee ole machine out for cleaning yesterday. I didn't try moving any parts just blew out the dust. I also removed a wireless adapter that I no longer use. Nearly 24 hours and no freezing.

I'll report back tomorrow, or earlier if it does freeze.

 

[clifford_cooley]

No freeze in nearly 24 hours. So it seems either I had a bad connection somewhere or the wireless card was causing trouble. If so freezing after installing Build 1703 was purely coincidence. I'll monitor another day and then I might try installing Build 1703 again.

 

[clifford_cooley]

Talking to you guys and getting responses back is helping me keep my temper down. I don't want to loose it like I did last time. Thanks to all for listening.

 

[Data]

No problem, from my part, the response to that is, you are welcome

Its Friday, if you loose it on Friday we are all doomed.

I'll monitor another day and then I might try installing Build 1703 again.

I wouldn't, wait for MS to decide to push it, and if it does , then do manual upgrade and not VIA WU.

Remember they are blocking the 1703 upgrade to some systems for a reason, and best let them have their reason so when its screwed up, no one can tell you, its your fault

 

[clifford_cooley]

I wouldn't, wait for MS to decide to push it, and if it does , then do manual upgrade and not VIA WU.

Remember they are blocking the 1703 upgrade to some systems for a reason, and best let them have their reason so when its screwed up, no one can tell you, its your fault

Ahh yeah, I forgot about that. That was probably for people that don't know how to deal with the machine (such as system backups and restores). That is Microsoft protecting themselves. And truthfully I don't blame them, not on that anyway.

But you are correct I should wait. The only reason I started installing 1703 was an update for 1703 that showed and wouldn't go away. I was like WTF, I don't have 1703! Why am I getting updates for a build I don't have installed. To be honest I took that as a sign that Microsoft was pushing 1703 at that time. Because I was waiting for Microsoft to roll out 1703.

 

[Comp Cmndo]

...I don't have 1703! Why am I getting updates for a build I don't have installed...

This...
https://support.microsoft.com/en-us...overing-windows-10-version-1703-april-25-2017

and/or this...
https://support.microsoft.com/en-us...ding-to-windows-10-version-1703-april-25-2017

 

[Trouble]

Talking to you guys and getting responses back is helping me keep my temper down

Still waiting and watching for the proverbial "other shoe".
As long as you maintain best practices and create disk images to support a good rescue / fallback position, I really don't see any risk in progressing through the various builds.
I do appreciate your patience in taking your time and observing each major build's behavior and performance on your machine.

I suppose that at some point we will learn that there are some machines that will just not run 1703 for some reason or other, but....
I'm not overly optimistic that we will ever find out exactly why.

They've recently dropped the number of Windows Phones that will be eligible to receive the Creators Update to a small hand few of models, without much by way of explanation as to why.
While I was happy to see my principle two models still on the list, I have a couple that are not and then there are some vague rumors about how "unqualified" phones can still get it.

But then I have a pretty primitive machine, dedicated to the Insider Preview program that seems to just keep on chugging along with whatever Microsoft throws at it, so IDK.... maybe we'll find that it's some obscure, currently unknown chipset problem or a memory controller or processor or combination of multiple factors that will require a firmware update that will probably never come as the hardware involved is no longer getting anything from the manufacturer.

 

[clifford_cooley]

Which is why I took it Microsoft was pushing out the upgrade. I wanted build 1703 installed on my watch. I despise Microsoft having Windows Update download an update for which I will do manually. That's twice the bandwidth for the same thing.

 

[clifford_cooley]

I do appreciate your patience in taking your time and observing each major build's behavior and performance on your machine.

With freezes and BSOD's, I feel that waiting and watching is my only option. Trial and error, while waiting for the next system hang.

 

[clifford_cooley]

Three whole days and no freezes.

 

[Trouble]

So..... what version on you currently running?