Windows 10: Microsoft Fixes the Windows 10 Freezing Issues

Read more: Microsoft Fixes the Windows 10 Freezing Issues - Thurrott.com

See also: Cumulative Update KB3176938 Windows 10 build 14393.105 - Windows 10 Forums

 

PC World has a similar report as well with pretty much the same title. Microsoft fixes Windows 10's Anniversary Update freezing | PCWorld

No such login freeze issue encountered here at all between the three desktops and three laptops while a fourth still needs to be looked at as for the lack of display issue.

:)

 

Windows 7 to 10 upgrade on a Dell Precision 390?

Hi Prahalad,

the graphics drivers install without any problems. The random freeze/hang issue is while running Windows 10 with the NVIDIA graphics driver.

Uninstalling the NVIDIA driver and installing the Microsoft Basic Display driver fixes the freeze/hang issue.

Thanks.

 

Why is the Anniversary update still publicly available for download!!!!!

Windows 10 Anniversary Update can cause PC to freeze, but Microsoft has a workaround

This is just one of many sites Quoting Microsofts response to this problem.

In case you cant read...

"Microsoft has received a small number of reports that Windows 10 computers freeze after upgrading to Anniversary Update.

The US technology firm has admitted that computers with the Windows 10 operating system stored on a solid-state drive and applications and data saved to a separate drive can run into issues.

Some users saw their systems freeze whenever they clicked on the Start Menu, or tried to load an application from the taskbar.

The freeze does not occur when Windows 10 is started in Safe Mode.

Microsoft says it is looking into a permanent solution for the problem, but in the meantime, has offered a temporary fix."

There is a problem and Microsoft has admitted it. Take your propaganda elsewhere buddy!

 

I was getting periodic freezes on two of my systems and this update seems to have corrected the problem. Keeping fingers crossed.

 

My bootup, freezing issues have disappeared since installing the latest update.

 

After this Update, there are still issues with external HDD. I was making a System Backup and system froze nearby the end. Sometimes pressing the "eject" Button there is no message "safe to remove". Sometimes connecting the HDD, Explorer does not Start automatically. This is random, I can not reproduce it.

 

I've been having random freezing but no loading issues on the win betas since forever or at least almost 1 yr. but not so much on the regular 1511-th2 and the 1607-AU builds here on the other PC's here .
or this one on the OEM HDD w/ 1706-AU I rolled in and running 14915 right now on an SSD .




Not seeing all that drama with this new PC in my specs for nearly 1.5 weeks since new now except occasionally in Chrome that can do that on it's own in a heartbeat anyway......... but not nearly as frequently as Edge .*sarc


The PC this replaced was a 6 yr old upgraded HP Pavilion AMD AM3 platform ,Phen.II x6 CPU on the OEM mainboard known to have a lousy nvidia chip set . That main board fried a couple of weeks back to the day and my have been deteriorating all along but it was performing well until it's sudden death at turn on from a regular shut down ,it mostly loaded windows then died .


Anyway if this hotfix-update helps us out I'm all for it .*092

 

I had random freezing's before the update but it seems to have been corrected*Wink

 

I have a few 2TB Seagate expansion desk ( USB drive ) and migrated some data ~ 280GB to one last week .I was scraping data out of my old PC that fried its mainboard this PC in my specs replaced ...........no problems moving the data or any other time when I clean instal these win betas and park the data ,desktop ,folders and files on that drive and bring it back here to the SSD in this new test mule in my specs and the one I used before that and re install the exe. programs . I just did that thurs nite clean installing 14915 .

 

That's an Insider build not the RS1 which has been seeing problems. So far haven't been seeing any problems on either the main or remote secondary with each having an external enclosure(main has fan cooled model) with a 1tb drive in each. Those had been pulled out of the main some time back when moving to a pair of 2tb server class drives and generally left off when not in use and especially when going from build to build allowing for each to have it's own fresh detection.

That seems to avoid any hangups or hangovers when going build to build while the remote desktop is presently in standby mode as far as the Preview builds go.

 

This update was installed on my machine on 1 Sept but the freezing continues. I read that the bug strikes machines with an SSD holding the C: drive, and personal files on an internal rotational drive, as in my case. (My programs are also on the SSD).

Mr. Thurrott advises (see text below) that if the bug continues, create another admin account and the original account will be cured. However, the process of creating another admin account includes the steps shown in the attachment which includes setting an email address and a password. My computer shop set up my new computer specially to make me the administrator without a password or other signing in stuff (I am as sole user). I really don't want to risk ending up with complicating the simplicity of my present method of just starting or waking without any need ever to sign in.

Would it be possible for me to delete the second account without messing up my own admin account?

How to proceed please? Thanks.


Mr. Thurrott: "And if for some reason you’re still experiencing freezing problems after all this, Microsoft recommends creating a second administrator account on your PC, and signing in to that account. Once you do so, your regular account should work fine again."

 

The only bug first seen with the Threshold 2 update after a couple of months and now returned once again in the RS1 update brings up what was first not found solveable until the repeat performance resulted in finding a deeper hidden MS Answers replay to one two page thread pointing to a WinHelpOnline reference that outlines the lack of a folder descriptions entry in the registry that had been replaced previously by the available Insider build at the time and not seen until the RS1 arrived in all that time! http://www.winhelponline.com/blog/er...rs-windows-10/

The VMs would be stubborn at seeing the automatic sign in at startup but never froze up during boot. That was recently remedied however with one of the RS1 still preview builds.

 

All that sounds very plausible and noting my new Haswell Core i5 PC in the specs runs a lot cooler by very nearly half at the CPU with the same workload and much cooler on the mainboard and overall inside in a larger HP OEM case. and no freezing on 3 other Intel PC's here .

I'm not seeing any random freeze problems on the 14393 .rs1 AU on this new PC in my spec. or 14915.rs on this SSD or using the external storage or 14905 same configuration when I rolled that in from an ESD I had despite it's other issues .

No freezing on 3 other Intel CPU PC here including 2 Core i7 and even after asking family users when they were on ..10586 th2 and now on 14393 .rs1 AU .

OTOH my 6 yr old HP PC now with a fried mainboard & AMD II x6 had the random freeing since at least the first th.2 builds stable or beta (didn't matter) all along up to 14905 before it fried that mainboard and I got this new Haswell Core i5 desktop delivered on 08.24.16

The dead upgraded 2010 HP /AMD PC was not particular about which Windows 10 OS to freeze including the betas or which HDD or the SSD or storage drive being used it would freeze on either .

That HP/upgraded to AMD Phen. II x6 and other upgrades and new storage drives along the way was at the end of its plausible upgradability and was 2010 AMD Phenom II x6 K10 ancient but SRSLY not bad outside of the random freezing with the faster than metal SSD in it .

I never saw the loading /log-on freezing at all though and that old dog would randomly freeze without warning and spike CPU and HDD use and take at least a minute or so to recover and not seeing that on the 3 Intel PC's here all along I was finally prompted to shop a new Intel PC anyway.*really

I was actually very nearly about to order this new PC when the old dog died anyway for the usual Intel performance , UEFI advantages today and the newer Haswell plus Intel CPU instructions and so on . .

AMD doesn't have anything plausible for me anymore ,YMMV even their room heating Flagship FX CPU gets bested by at Intel Core i3 in PC gaming .

I just pulled up the most favorable bookmark and ordered it and it was here 4 days later and no random freezing in this one dual booting 14393.rs1 AU I rolled in on OEM /OS & metal and clean installed 14915 on the SSD I put in it .

I paid my AMD dues more than once and regrettably a Pentium 4 when they were new , I'm done with AMD fior now and I never had a PC for 6 years for my daily driver & upgrades notwithstanding anyway .*really

 

The problems you described there weren't from AMD but the HP board going toast on you. As far as the main I will be keeping the RS1 on that while the second saw the 901 rolled back to the RS1 when going to examine the Recovery option. That went as if there hadn't even been any 901, 905, or 915 Insider build on at all there being one thing on the list of items to check off before seeing the Get insider builds option restarted again.

Here I have been running with the Phenom II Black Edition 965(dual core) first in the main replaced by the 975(quad core) having missed out on the 980 and moved the 965 into the second desktop used remotely as well as for testing and not one iota as far as performance hits. When considering the if and when for the next new build I would be pondering on the much newer Octocore(8 core) type series cpus since AMD has always had a work horse cpu that generally runs cooler to begin with.

As for the bulk of people running into log in freezing as well as problems with sticky driver issues I mainly here that from those running Intel and NVidia graphics while haven't been hearing hardly any AMD/ATI Catalyst type issues as had been seen in years past I hate to see AMD going south however since I've been pushing the main quite a bit harder at times then the test build ever sees despite upgrading a few things like how much ram and adding in a larger drive. Still have 7 as well as 10 running on both as well while it seems as though 10 will be taking over since 7 is now hardly been booted into except for a few tests at times with 3rd party wares.