Windows 10: Windows 10 22H2 - Sept KB5043064 - StartMenuExperienceHost.exe error

Afternoon All, Has anyone experiences Application event log error 1000 startmenuexperiencehost.exe recently after installing the latest KB5043064. W10 22h2. It appears to have no impact on the user experience, no crashing of the start menu or anything like that but it does continue to leave a trail of crash events when the start button has been activated by the user. Remove the KB and the crash events stop. Re-install, they start again. This doesn't appear on all device with the KB, so leads me to believe this is software on the device having compatibility issues. I was interested t

:)

 

How to get the Windows 10 2022 Update version 22H2 Win Update

If you can't install it from windows update you can try to install it manually, it's the same KB5015684 obtained with windows update. Windows 10 Version 22H2 is coming in October 2022 ---> KB5015684 Provides Quick Windows 10 22H2 Upgrade - Ed Tittel On the Ed Tittel page click on the links DeskModder.de or .MSU x64 version of the upgrade. KB5015684 Funktionsupdate auf die Windows 10 22H2 (19045) [Manueller Download] - Deskmodder.de Do dism and sfc /scannow commands before and/or after installing it.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

How to get the Windows 10 2022 Update version 22H2 Win Update

I wish things are that simple. My error code was 0x80246017, and I don't have KB5020435 installed so it's a dead end. BTW, MS lists like 6 or 7 error codes of the format 0x8024xxxx on the "troubleshooting WU problems", and when you chose next step, it suggests generic steps: run WU troubleshooter, check if your disk has no errors, is your remote disk is accessible, etc. Same as MS community; each similar error has completely different cause and (re)solution. MS in notorious for this- if it works then OK, if it doesn't then good luck.