Storing Cookies (See : http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm ) help us to bring you our services at overunity.com . If you use this website and our services you declare yourself okay with using cookies .More Infos here:
https://overunity.com/5553/privacy-policy/
If you do not agree with storing cookies, please LEAVE this website now. From the 25th of May 2018, every existing user has to accept the GDPR agreement at first login. If a user is unwilling to accept the GDPR, he should email us and request to erase his account. Many thanks for your understanding

User Menu

Custom Search

Author Topic: Windows Update may have broken my PC  (Read 3990 times)

harrykane140693

  • Newbie
  • *
  • Posts: 1
Windows Update may have broken my PC
« on: October 25, 2018, 09:17:38 AM »
I got the laptop to work again by doing the reset or whatever. Its the one that reinstalls windows 10 but keeps your files. Thanks for all the help.

So updated and restarted my laptop today and things have kinda gone down hill since then. First thing that happened when it appeared to finish I was presented with a prompt to select a keyboard. Afterwards I was presented with several options and it seemed like the update somehow corrupted my os or system32. I tried using another system since it was an option and I was presented with two Windows 10 os both version 3, I picked the second one and i was brought to my login screen with my username and icon. I could login and got the windows "we are updating" notice. Afterwards i was greeted with a c:\windows\system32\config\systemprofile\desktop is unavailable. After that I assumed I lost all my data but when I booted it into safemode I could see my shortcuts that were on my computer and I also didnt get the error. However if I created a file and tried to open it i would be greeted with an attempt was made to reference a token that doesn't exsist. Im assuming my data isnt gone its just inaccessible currently. Any ideas how to fix it currently? I noticed both on this subreddit and on twitter that im not the only one with this problem so Im sure I may just have to wait until Microsoft fixes it.