Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Thursday February 13 2020, @09:30PM   Printer-friendly
from the At-least-this-time-it-was-not-actually-deleted dept.

Reports are coming in that the Windows 10 KB4532693 cumulative update is loading an incorrect user profile and causing the user's desktop and Start Menu to be reset to default.

On February 11th, Microsoft released the Windows 10 v1909 and v1903 KB4532693 cumulative update as part of their February Patch Tuesday updates.

Since then, reports are starting to come in that after installing the update, some users state that their normal user profile is missing, their desktop files are missing, and everything was reset to default.

Here are links to some of these reports:

[...] The good news is that the update is not wiping your data, but rather renaming the original user profile in the C:\Users folder. If you are affected by this issue, you can look in C:\Users and see if you have a renamed profile ending in .000 or .bak.

Unfortunately, restoring a profile through Registry edits may be a very difficult and risky task for many people.

As some people stated that they could resolve the issue by restarting Windows a few times or uninstalling the KB4532693 update, it is safer to go down this route first if you are affected by this issue.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1, Interesting) by Anonymous Coward on Friday February 14 2020, @06:16PM

    by Anonymous Coward on Friday February 14 2020, @06:16PM (#958224)

    I have no clue and I wish more people would post and respond to these types of posts rather than ranting and whining about things we already know (Stop using SoylentNews as your emotional dumping ground please. Get a real friend for that).

    My only guess is when testing patches, the developers generate a new profile and apply the patch under that user so if something goes wrong then it doesn't screw up their real profile. Somehow some of that testing harness got left in. Instead of picking the test profile, it cloned the only profile reference on the machine, renamed the original profile folder since there's probably a bunch of random changes you'd need to do to truly rename a profile and temporally removing the existing one is easier, applied the cloned profile, installed the patch, deleted the cloned profile, and forgot to restore the original profile.

    But I could be completely wrong. And the fact that you could end up with a .000 or a .bak sounds simply crazy. That means two different systems might be renaming the profile. No one writes backup software which randomly decides to use different file extensions.

    Perhaps Windows realizes the profile has been deleted and attempts to restore it from a restore point or something?

    I really miss the GoBack software. It gave you a log of every file change occurring on your system. That would have been interesting to see in this case.

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1