@panchop Run the System File Checker (SFC) tool to scan and repair corrupted system files: Open Command Prompt as administrator. Type sfc /scannow and press Enter.
not sure did a fresh install of 26100.4562 weird hangs going into the Gui for 1st time then after it is ok must be oobe working or something then I notice print to PDF is back
I still got "store component it's repairable" after doing in place upgrade. Might need to do a complete reinstall.
Code: amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.0.26100.4762_none_322626e3e83242a9.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26120.26100.4762_none_555ae93b285bfd5a.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26121.26100.4762_none_44ac581fc161d701.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26141.26100.4762_none_662563009bb9b53f.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26142.26100.4762_none_5576d1e534bf8ee6.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26143.26100.4762_none_44c840c9cdc5688d.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26144.26100.4762_none_3419afae66cb4234.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26145.26100.4762_none_236b1e92ffd11bdb.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26200.26100.4762_none_77990ba47778b705.manifest amd64_microsoft-product-d..coreuap-versioninfo_31bf3856ad364e35_10.26201.26100.4762_none_66ea7a89107e90ac.manifest Spoiler: amd64_microsoft-ge-client..es-26200-enablement_31bf3856ad364e35_10.0.26100.4762_none_377e1abcf0725fff.manifest Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Ge-Client-MonthlyBundles-26200-Enablement" version="10.0.26100.4762" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <registryKeys> <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\15\1230538894"> <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" /> <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\15\1398311054"> <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" /> <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\15\1633192078"> <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" /> <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\15\815149711"> <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" /> <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> <registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\15\882258575"> <registryValue name="EnabledState" valueType="REG_DWORD" value="0x00000002" /> <registryValue name="EnabledStateOptions" valueType="REG_DWORD" value="0x00000000" /> <securityDescriptor name="WRP_REGKEY_DEFAULT_SDDL" /> </registryKey> </registryKeys> <trustInfo> <security> <accessControl> <securityDescriptorDefinitions> <securityDescriptorDefinition name="WRP_REGKEY_DEFAULT_SDDL" sddl="O:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464G:S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464D:P(A;CI;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CI;GR;;;SY)(A;CI;GR;;;BA)(A;CI;GR;;;BU)(A;CI;GR;;;S-1-15-2-1)(A;CI;GR;;;S-1-15-3-1024-1065365936-1281604716-3511738428-1654721687-432734479-3232135806-4053264122-3456934681)" operationHint="replace" /> </securityDescriptorDefinitions> </accessControl> </security> </trustInfo> </assembly> 1230538894: 54237988 1398311054: 54237993 1633192078: 54238000 815149711: 57048216 882258575: 57048218
Yup i got this info screens at start, but it looks like it works normal after click ok on these. I think it pops up when U have some parts of start menu or settings elements disabled via GPE I have home disabled via GPE but it still work as before update.
go into settings/system/recovery choose fix problems using windows update, it will download a repair version of your current build If you want a fresh look in update after the repair run this as a .bat file and reboot before choosing fix problems using windows update or after ..its up yo you Running chkdsk before hand is a good practice before running repairs You could try repair the component store: Repair-WindowsImage -Online -RestoreHealth Code: @echo off powershell -windowstyle hidden -command "Start-Process cmd -ArgumentList '/s,/c,net stop usosvc & net stop wuauserv & del %systemroot%\SoftwareDistribution\DataStore\Logs\edb.log & del /f /q C:\ProgramData\USOPrivate\UpdateStore\* & net start usosvc & net start wuauserv & UsoClient.exe RefreshSettings' -Verb runAs"
@boe323 thank you for that. I'll see what I can do, my windows 11 is not compliant as I use @Enthousiast script to install windows 11.
This one fixed GPE errors for me, try it. Spoiler: GPE fix C:\Windows\PolicyDefinitions\en-US\Desktop.adml > Delete the following: By default, a user can change the location of their individual profile folders like Documents, Music etc. by typing a new path in the Locations tab of the folder's Properties dialog box. <string id="EnableThemeFileRemoteResource">Allow theme files from network locations</string> <string id="EnableThemeFileRemoteResource_Help">This policy setting determines whether remote paths can be used for resources inside of a Windows desktop theme (.theme/.themepack) file.</string> C:\Windows\PolicyDefinitions\Desktop.admx > Delete the following: <policy name="EnableThemeFileRemoteResource" class="Machine" displayName="$(string.EnableThemeFileRemoteResource)" explainText="$(string.EnableThemeFileRemoteResource_Help)" key="Software\Policies\Microsoft\Windows\Themes" valueName="EnableThemeFileRemoteResource"> <parentCategory ref="windowsesktop" /> <supportedOn ref="windows:SUPPORTED_Windows_11_0_22H2" /> <enabledValue> <decimal value="1" /> </enabledValue> <disabledValue> <decimal value="0" /> </disabledValue> </policy>
When problems occur with updates, mostly it is caused by to much "cleaning up" and then a repair/replace upgrade with an uptodate ISO should fix it.
25H2 is not finished yet. Use it if you want to test it on the Dev Channel. Otherwise stay on stable 24H2.