Forum Discussion
SystemSettings.exe crash after install KB5031354
Hello all,
We use the GPO-setting "settings visibility page" to show only those settings that are necessary for our users. After the installation of KB5031354 all was messed up and the defined settings were not displayed anymore.
After further investigation I found that the problem is related to a crash of the "systemsettings.exe". I believe that this app crash can be reproduced on any Windows 11 Enterprise/Pro where KB5031354 is installed. The steps below were executed on a clean fresh install of Windows 11 Enterprise 22H2 (English) with all the latest updates installed, including KB5031354.
-
Create the following registry key. This is the equivalent of the GPO "Settings visibilty page". [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer]
"SettingsPageVisibility"="ShowOnly:yourinfo"
-
Open the Settings app
A blank window will be briefly displayed. 2 new events are created in the Application event log :
Error - Application Error - Eventid 1000 - Application Crashing Events
Faulting application name: SystemSettings.exe, version: 10.0.22621.2428, time stamp: 0x3a143f4b
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22621.2361, time stamp: 0x5d88d3ddException code: 0xc000027b
Fault offset: 0x0000000000872280
Faulting process id: 0x0x1118
Faulting application start time: 0x0x1DA02705595E075
Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 3226300a-7628-454c-9694-75ac4735f188
Faulting package full name: windows.immersivecontrolpanel_10.0.6.1000_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel
Information - Windows error reporting - eventid 1001
Fault bucket 1263439590791464883, type 5Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: windows.immersivecontrolpanel_10.0.6.1000_neutral_neutral_cw5n1h2txyewy
P2: praid:microsoft.windows.immersivecontrolpanel
P3: 10.0.22621.2428
P4: 3a143f4b
P5: combase.dll
P6: 10.0.22621.2215
P7: 05b9e9b5
P8: 8000000b
P9: 00000000000901cb
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.98037898-2ae9-4911-a29a-7cd50ea64ae6.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7106987b-61a9-4713-8487-b57fdf7576c1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8eca01d3-aa6b-40b3-9627-fcabaa2cebd3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.03b2ccf3-63f1-47cd-b75a-85cb28372fbf.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9aa2daaa-cce4-4b9f-b2de-a38410a0dbe2.tmp.xml
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_windows.immersiv_f37a9be9bd0bd3b3db1ba0c18d5b7ef6f73ad1_06ae74d7_4a1faeb3-83ef-456d-a34a-6ee3bb41a823
Analysis symbol:
Rechecking for solution: 0
Report Id: 3226300a-7628-454c-9694-75ac4735f188
Report Status: 268435456
Hashed bucket: 5a818803056a40647188a39d244a47b3
Cab Guid: 0
When KB5031354 is uninstalled there is no crash anymore of "systemsettings.exe" and the Settings app can be used again. The setting "yourinfo" will be the only setting that is displayed (cfr registry setting).
I contacted M365 support (2310121420000904) and they told me to submit the issue through the feedback hub with my personal microsoft account (?!?). There has been no response, no questions, no feedback and no status updates. After a post in the microsoft community I was redirected to this tech community ( https://answers.microsoft.com/en-us/windows/forum/windows_11-wintop_update/gpo-setting-settings-visibility-page-not-applying/7b363dda-1364-4611-adce-6ae68451a801?messageId=cd5478e0-c157-43da-a52c-59675456ff94 ).
Hopefully more response/support here 😉
Grts,
Tom
-
After the installation of KB5032190 the GPO-setting "settings visibility page" is applied correctly again. There is no mentioning of the above bug in the release notes, improvements or highlights.
Anyhow, install KB5032190 to fix above bug.
Grts,
Tom