Question

Corrupt file in Windows 10, nothings is working..

Yesterday my pc with windows 10 installed was working fine, turned it off and i went to sleep.
Today, i boot it up and i logged in my user account, i entered the password and it took more time than normal to go into the desktop, when i finally got there, my background photo was missing, i could only see all my icons and a black background, i could move the mouse but nothing was opening, if i double clicked anything the computer would only freeze and had to restart it.

I tried to use a system restore point made automatically two days ago, everything was going normal but then it stopped with a error saying that a file called appdb.dat failed to extract, it was located at %USERPROFILE%\AppData\Local\ Microsoft\Windows\Notifications\appdb.dat, {ComputerName}_appdb.dat.

After that ive been trying a lot of diferent solutions and nothing works, i tried sfc.exe, dism.
Originally when i build my pc i installed win 8.1 from a disc, so tried booting from it and refresh the pc, but that didnt work because it said that the drive where windows was installed was locked, so i came back to win 10 and i tried doing a system restore choosing the keep my files options but at 40% it stopped and said that an error ocurred and no changes were made.

I cant access any file or folder in my pc, nothing, all i can do is open command propmt with shift+restart, safe mode wont let me access anything neither. I literally have no idea what could i do. Any help, advice or idea to fix this?

Discussion is locked
Follow
Reply to: Corrupt file in Windows 10, nothings is working..
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Corrupt file in Windows 10, nothings is working..
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Comments
- Collapse -
Answer
Let's watch this other thread too.
- Collapse -
Answer
Not enough is known about this file.

CNET Forums