Windows 10: Update issues

After a mandatory update the computer won't boot up anymore.

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

User.000 issue after updating to 1909

I'm one of the many people suffering from issues with user profiles after applying Update 1909 to Windows 10. I've read all the threads I can find on the topic here and have followed the suggestions, all to no avail. Any other thoughts are appreciated.

After applying Update 1909, the ProfileImagePath was changed to c:\users\User.000
One file that was always in use and couldn't be removed was left in c:\users\User (can't recall or find the exact file now), so I could never rename or remove the c:\user\User directory.

I followed the multiple suggestions from Brink and others:

• Rebooted at least 6 times
• Enabled hidden Administrator
• Booted into Safe Mode
• Changed ProfileImagePath
• Tried to rename c:\users\User but couldn't because a file was still in use
• Copied all data from c:\users\User.000 into c:\users\User
• Rebooted and had temporary profile
• Followed steps in Brink tutorial to change ImageProfilePath; rebooted with no change
• Restored using Restore Point from before Update 1909 - returned to single profile state (User.000)
• Removed each update that was installed individually and rebooted after each update removal - profile state never changed
• After all updates were removed, repeated the steps above with hidden Administrator, changing profile, etc. - same issue with file in use in c:\users\User
• Followed all steps above with hidden Administrator but without copying files from User.000 to User - same results

Any suggestions are greatly appreciated!

 

MSI 5870 BIOS Update

Still can't reproduce. Could you please post the exact BIOSes that produce the issue?