Windows 10: Windows 10 Anniversary CLEAN install: a nightmare!

I'll try to keep it short.
I did a clean install of Windows 10 anniversary on a new SSD 240 GB and all the drive detached.
I did it 3 time and now it's 10 days I'm working on it to have an working OS.
The actual problems are:
1) keep freezing both file explorer and Chrome (same with Edge)
2) No crash or BSoD.
3) I "only" have to wait... from 10 second to 1 minute to have the things done.
E.g. menu start: all completely blank and stuck
click on Control panel icon and wait 30 second to have it open
open Chrome and nothing happen (if I click newly after "X" seconds 2 Chrome pages appear)
Taskbar frozen in both monitors
Thumbnail of the taskbar for open app or folder empty and then frozen the bar.
Unresponsive folder
All these problems have a lasting from a few seconds up to a minute.
I've installed by Mediatool X64 via USB with Win 10 Anniversary with no problem at all.
Then I moved using Windows itself the folders Documents, Music, Download, Movie and pictures each one in a partition leaving the folder User including AppData in C:
I also moved to a dedicated partition (my scratch partition) pagefile sys, indexing windows.edb, INetCache, chrome history and I deleted Hiberfile.sys as always.


Every time I changed something, I restart and test all: no problem at all excluding continuous blocks (unresponsive and frozen).
Then I installed Office 2016 and Adobe CC 2015, Calibre, 7Zip, Chrome, Macrium and I did my first full recovery image (with Windows and Macrium).
It seemed the frezing was a bit less, but still was present.
The OS access was and is very fast, but when I'm in I have to wait to click on start or immediately freeze.
The last thing to do was to install my Eset Smart security that I left for last, knowing that Windows does not love you exclude Defender.
I tried for days, I've installed and uninstalleled at least 5 times but If Ive Eset running I cannot navigate on Internet *Sad


And, last but not least, the event viewer lists an incredible array of errors and warning most of which appears to be linked to the drive 0 ie that of the OS.
Some errors seems to be linked to application I still haven't open as Office or Adobe.
The Kernel-EventTracing for today reports:
Session "Pku2uLog" failed to start with the following error: 0xC0000035
Session "NegoLog" failed to start with the following error: 0xC0000035
Session "IDListenLog" failed to start with the following error: 0xC0000035
Session "P2PLog" failed to start with the following error: 0xC0000035
Session "HomeGroupLog" failed to start with the following error: 0xC0000035


SideBySide:
Activation context generation failed for "C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Microsoft Office\root\Office16\UccApi.DLL" on line 1. Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="16.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="16.0.0.0". Please use sxstrace.exe for detailed diagnosis.


Kernel-Power
The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.


Application Error are all for Microsoft Edge (event ID 1000 task 100)


Service Control Manager are all for Google:
The Google Update Service (gupdate) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion. OR
A timeout was reached (120000 milliseconds) while waiting for the gupdate service to connect.


DistributedCOM (event 10010) has errors with
The server {0002DF02-0000-0000-C000-000000000046} did not register with DCOM within the required timeout.
and (event 10016)
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.


A total of 307 errors, 899 warning, 5516 information, 11960 Audit Success since Friday, August 26.


The update are all done including the one of September 1st, which was to resolve the Windows 10 freezing issues, but it has done absolutely nothing to mine.


Now my question are:
1) How to solve the "freezing" issue.
20 How to install my Eset Smart Security.


Please help me, I'm really in trouble now: I did 3 clean install with the same situation and I have no idea
what I can do now :'(
Thanks a lot


:)

 

anniversary update for windows 10

does anyone like the new anniversary update for windows 10..heard it's a nightmare

 

anniversary update

does anyone like the new anniversary update for windows 10?? i heard it is a nightmare...

 

Hi, can you confirm that Win 10 build 1511 worked ok on your PC?

Note that a number of issues have been widely reported for some users with the anniversary build, including freezing problems. This is the only issue I know of for which MS has yet issued an update.
Microsoft Fixes the Windows 10 Freezing Issues - Windows 10 Forums

If you can confirm the previous build works but the anniversary build not, you would be well advised to stay with what works for you for now, and if you have the Pro build, defer updates.

 

Thanks for the quick reply.
In my case Win 10 build 1511 (November update) failed to install.
I was still in Version 10.0 (build 10240) because every time I tried to upgrade via Windows update or via mediatool, after having the advise "Your update is ready. Your PC needs to restart to complete the update" at the restart nothing was done.
Same for version 10586. It's for this reason I decided for a clean install and I'm now in version 1607 (build 14393.105).

I was perfectly aware of the problems for this version, I'm following more than one forum about the situation about this update. But I choose the clean install and I was hoping the new OS was OK!
Reading online the most part of these problems are linked to the update not to clean install.
And to avoid problems linked to partition and so on, I unplugged all the SSD and HDD leaving only the new SSD for the OS.
I saw the post by Swan about the update for fixing the freezing issue, and I also read on Thurrott.com about the possibile solution creating a different administrator account; but before I make that attempt which nobody confirms as helpful, I wanted to see if others have similar problems with a clean install.
And I keep looking online.

Thanks *Wink

 

What I suggest is to try a clean install of 1511 and see what happens. You had 10240 on your PC, but as I understand it, the upgrade failed, but you didn't try a clean install. Do that without doing updates during the installation. You can do those later.

That's the only thing I can think of in case you are experiencing freezing issues with 1607.

 

one thing to try and do as wel, l when you install new O/S use cat5 instead of wireless ...

 

I understand your opinion, but I think it would create more trouble.
Install an OS already surpassed in place of the new one (the Anniversary one) that in fact is not an update but a new OS, seems to me really weird.
Also because we already know that Anniversary as update gives many issues.
And, over all, I cannot believe that Windows can make such a mess!

But, thanks anyway *Smile

 

Thanks for your suggestion, but my PC is a desktop PC and I'm on ethernet Cat7. *Smile

 

- simply to avoid potential issues with the anniversary edition to see if you can install Windows without the freezing issues you stated you have- which is a characteristic of 1607 for some.

That's not weird, it's simply a logical option. No one said it was ideal.

Then if you have pro, you can defer the upgrade and try that later.

 

If you have a spare hard drive I would swap it out and and try a clean install. See if the freezing conditions.

 

plausible *really

OTOH my longstanding random freezing cure was the new PC in my specs but the OP has more swift Intel PC than all that ,my Core i7 Game /Daw box or a lotta folks . Maybe I would see if a PSU voltage rail is heating up and sagging also or maybe a mainboard VR or loud OC is going south *really

FWIW the random freezing became more frequent as my 6 yr. old HP AMD K10 II x6 OEM PC mainboard presumably deteriorated before it blew up 3-4 wet lytics near the CPU heatsink trying to load windows *really
I might fix it and pass it along ,it wasn't bad for everyday computing ,DVD transcoding or 1080p video and had 8 GB of ram and a newer HDD and the AU ,some low ESR 105° lytic Caps like Panasonic's or Rubycon from Digikey or an AM3, AM3+ inexpensive or salvage mainboard will likely fix it .

As they say a little voltage or lack of can go a long way especially with a cattle prod where the sun doesn't come up *cry

 

TBH what D man says is entirely plausible and and nothing that isn't done routinely especially in winbeta world , it's impossible to validate a given biuld on all the variable configurations out there and that moreover includes customs & unusual or uncommon configurations or HDWE pairings and maybe a loud Game OC / + voltage at CPU and or d/GPU and maybe memory . OTOH a DVM and voltage rail check for PSU rail sagging or a bad ground would also be plausible if it's unstable on any other OS in there *really

A clean install can fix many things including random freezing (just ask around here ) and is the only best way to instal windows period or establish a legitimate base point for diag anyway and should have been your first remedy attempt if it wasn't followed by a *clean roll back like D man says if those clean install (s) didn't work it's not unheard of and you could sit it out for the duration for another build .

IF MS has your telemetry on an uncommon aftermarket configuration and custom random parts pairing that is causing this don't put any money on a finish resolution anytime soon if at all they likely go for broad market OEM retail, CTO or common custom OD vendor configurations out in the field first *092.

IOW If you beta test that's always a contingency ,rolling back nothing weird ..........all of it just is or isn't in beta testing without an out of hand fix or an official fix or a reg hack or file hack or string ( *that works ) and may equally apply to the AU *Cool

OTOH there are some new found issues out in the field with some (a lot) of Samsung SSD's so maybe you might want to Google search all that drama and see if your SSD is one of those *Eek

I've maybe done it both ways ,clean install and upgrade dirty and easy more times than you can count on 10 hands and then more than that since win 3.0 and DOS and I've seen DIY /ODM configurations and upgrades that all together without a HDWE and or driver change just wouldn't work on any given win OS .
ppffttt I could write chapters about dial up modems,modem strings and persistent IRQ things .

FWIW my critical daily driver PC and the family's PC are always new or passed from me validated HP PC's without exception and not the entertainment PC here beyond the web or media and the beta OS are always a separate drive. I don't do customs anymore beyond maybe significant upgrading of an assy line PC here like the Core i7 playing BF1 beta in the music PC game room addition right now or my driver at some point should the need arise .