Windows 10: Cumulative Update KB3206632 Windows 10 PC and Mobile Build 14393.576

This Update brook my Audio Support. IDT-Audio Driver will not install, on this Update.

Windows 10 1607.576_x64.

Going back to 1607.351

The problem was while performing a minimal Safe Boot , most of Windows Services were Disabled, thought I put it back to "Normal" but some how system did not activate all Services again.

 

During each cold boot of the .576 update (12/16) system I get several critical Edge errors, NO solution found by MS.





Any ideas?

Greetz

 

Do you have any problems using Edge? I stopped looking in the Reliability Monitor unless I notice a problem. I got tired of Reliability Monitor finding problems when I wasn't noticing any problems.

 

Thanks Winuser for your reply. I'm at least not aware of the (critical-error) malfunction of Edge, but still eager to address this issue because it is an Windows 10 native application with strange behaviour when viewing the Reliable Monitor.

Greetz

 

Same here on 2 desktops - stopped using Edge. Started using Chrome again and now have no Reliability Monitor problems showing. Shame MS can't get their browser to work as well with Windows 10 as others.

 

For now I switched back to Chrome (main) and IE for safe browsing whilst using ESET secure banking online!

I will look at RM again in january 2017!

Greetz

 

I'm starting to use Chrome as my main browser instead of Pale Moon. I only use Edge for testing in my Insider build.

 

Still using Firefox DE x64...chugging along nicely...no problems, either...

 

I had a lot of trouble trying to successfully install this update on a newly formatted ACER laptop. I think it needed five or six retries.

 

Update: Cumulative Update KB3213522 Windows 10 Version 1607 build 14393.577

 

This update went well. Much faster than previous updates.*Smile

 

I've just done two machines today, I tend to neglect the ordinary ones and only use the TP.

 

In reference to my post # 28, what I did to fix the issue (update hanging at 95 % on both of my PCs) was to go directly to Microsoft Update Catalog and downloaded KB3206632 from there. After that, everything went smoothly without any hiccup. Sure enough, Microsoft knew about the problem, so much so that they recently released a new update KB3213522 to replace the troublesome one (KB3206632).

From now on, I have decided to defer all cumulative updates until Spring 2017, exactly the time Microsoft is supposed to release Windows 10 creators Update. As a matter-of-fact, there is a way to defer all updates by going to gpedit.msc if one is running Windows 10 Pro edition or the enterprise edition...My reason for that is simple, I cannot afford to be loosing an entire day or two trying to fix problems with Windows updates.