- WINDOWS 10 START MENU SEARCH NOT WORKING 2022 HOW TO
- WINDOWS 10 START MENU SEARCH NOT WORKING 2022 UPDATE
- WINDOWS 10 START MENU SEARCH NOT WORKING 2022 WINDOWS
Open Procmon and configure the filter first as shown below When you are wondering what is happening in the registry, there is always Procmon!. But which ones? because we have a lot of them! That’s definitely one error (0xc000027b) we noticed before, right? I guess we have some missing permissions for “ALL APPLICATION PACKAGES” | AKA S-1-15-2-1 on some registry keys….
WINDOWS 10 START MENU SEARCH NOT WORKING 2022 HOW TO
When looking at the above link they do mention something about how to solve possible Store Apps issues.
WINDOWS 10 START MENU SEARCH NOT WORKING 2022 WINDOWS
Microsoft Store Apps fail to start – Windows Client | Microsoft Docs As always I also looked if there was something useful in the MS-Docs. If we don’t want to recreate the profile and go through all the hassle to resync OneDrive etc we also have another option to fix it.
WINDOWS 10 START MENU SEARCH NOT WORKING 2022 UPDATE
Please Note: With the June update released we also made sure that we installed the June 2022-06 update which has the Store fix included. After logging in, please open your OneDrive and Outlook to make sure your Microsoft account is connected and working again!
With the old corrupted profile gone we could start logging in with the user again so the profile will be recreated. After logging in we started deleting the c:\users\%username% folder and removing the user its profile key in the registry To do so we rebooted the device and logged in with a local admin user. At first, we just deleted the corrupted profile to make sure a new nice, and shiny profile would be created When this weird issue started occurring we didn’t know exactly what was going on. As shown below even the AAD sign-in log is giving us the same 0x80070005 Access is denied error This event log is showing us the Kernel-General event 16 mentioning the application history in component AppData\Local\Packages\_cw5n1h2txyewy\Settings\settings.dat is deletedĭamn… Almost forgot one event log! As told earlier, when you are having sign-in issues with Onedrive and Outlook it’s always best practice to check out the AAD event log. The Application event log is not the only event log we need to dig into so let’s also take a look at the System event log. But I am not done yet because another error caught my eye! As shown below, it is mentioning the 0xc000027b error. It’s pretty obvious we are dealing with 2147024891 | 8007005 | Access Denied errors. Repair of state locations for operation SettingsInitialize against package _cw5n1h2txyewy with error -2147024891 returned Error Code: 0 Triggered repair of state locations because of operation SettingsInitialize against package _cw5n1h2txyewy with error – 2147024891. Repair for operation LocalSettings against package _cw5n1h2txyewy with error -2147024891 returned Error Code: – 2147024891. Triggered repair because operation LocalSettings against package _cw5n1h2txyewy with error -2147024891. Now we know and have seen what stops working and if we didn’t break our device, we need to take a look at which events we would get if all that stuff breaks! Open your Application event log and start looking at all those excellent yellow warnings! Looking at all the stuff that is breaking, I guess we could just break the device and be done with it… but I guess we need to fix it, otherwise we wouldn’t be doing our job!
0 kommentar(er)
