However, it does not help and the Start menu still does not appear. I tried to restart the Explorer shell first. There can be multiple reasons for the broken Start Menu, one solution cannot fit everywhere. Win+X -> Control Panel -> User Accounts -> Manage Another Account.Now, assuming all is well, you want to delete the 2 accounts you created: Reboot, then sign back in with your original profile.Right click empty area in the folder, and select Paste.Right click "Database", and rename to "Database.BAD".Now, navigate to the same folder for your damaged profile (C:\Users\YOUR_USERNAME\Local\TileDataLayer).Right Click the folder "Database" & Copy.Navigate to C:\Users\TempAdmin1\Local\TileDataLayer (click "continue" to gain access when prompted).Open File Explorer, select View, then check the box marked "Hidden Items".Logout, and then login to the "TempAdmin2" account, using "password2" (note: you must fully sign out, not just switch users).Login to the "TempAdmin1" account using password "password1".Net localgroup administrators "TempAdmin2" /add Enter the following commands, in this order.Press WIN+X, and select "Command Prompt (Admin)". Or blow away the VM and rebuild from scratch (you don't think I let windows near my actual computer do you?!)īased on the above I found which lists the steps for replacing the corrupt db and a bunch of people saying it works. I suspect this means I'll have to create a new user profile and steal the folder from that. Report ID: b26367c9-d409-4a01-a801-7d8b0870ebb0įaulting package full name: _0.16384_neutral_neutral_cw5n1h2txyewyįaulting package-relative application ID: App Log of the thing that crashed when I renamed the folderįaulting application name: ShellExperienceHost.exe, version: 0.16425, time stamp: 0x55bec5f5įaulting module name: Windows.UI.Xaml.dll, version: 0.16431, time stamp: 0x55c9bf27įaulting application start time: 0x01d0fbbac66ae74aįaulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exeįaulting module path: C:\Windows\System32\Windows.UI.Xaml.dll If this condition persists then please restore the logfile from a previous backup. The read operation will fail with error -501 (0xfffffe0b). This logfile has been damaged and is unusable. Data not matching the log-file fill pattern first appeared in sector 238 (0x000000EE). The failing checksum record is located at position END. Conculsion - win 10 is buggy and I should have stuck to windows 7. I renamed folder C:\Users\tim\AppData\Local\TileDataLayer\Database which crashed something, and now I can open the start menu but it's completely empty.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |