Enabling CSM does not necessarily mean you will lose the UEFI/GPT boot mode, in most cases you will still have the option to boot in UEFI mode. What you lose is the "pure" UEFI boot. Case in point: I'm still dual booting Windows XP and Windows 10 (in UEFI mode from a GPT formatted drive) on an old desktop machine.
IObit Uninstaller does a fairly decent job, IMHO, and lets you decide which apps to nuke. There are certain hardware related apps that I want to keep.
That's a bit of an exaggeration... you'd want to run at least a proper "debloat script", e.g. Sophia (a version for LTSC is available as well), which also applies a variety of performance tweaks. And you'll still have to deal with telemetry and other minor issues... guides are plentiful.
It depends a lot on your motherboard / computer vendor Most laptops that I've seen from Dell, Acer, Toshiba, when you enable CSM, you can only boot in legacy mode (MBR partition scheme). But on most dyi desktops you are right. You can still use UEFI boot with CSM enabled. But I don't know any system apart from some Windows 8 intel atom tablets that provide UEFI 32bit support so he will still need to have a MBR partitioned hard disk
I had on my Tech computer bench and my MSI laptop did report, I just Click 'X' that all.. BTW, I know get around bypass TPM clean install. and disable Network connection Flow by kill task manager during processing installing Local Domain instead Microsoft account!!
How about? Code: powershell -nop -ep bypass -c "Get-WindowsUpdateLog -LogPath %temp%\temp.log -ForceFlush -Confirm:$False -ErrorAction SilentlyContinue" @wmic service usosvc call StopService @wmic service wuauserv call StopService @del /f /q "%WinDir%\Logs\WindowsUpdate\*" @del /f /q "%ProgramData%\USOPrivate\UpdateStore\*" @del /s /f /q "%ProgramData%\USOShared\Logs\*" @rd /s /q "%ProgramFiles%\UNP" @wmic service wuauserv call StartService @wmic service usosvc call StartService @UsoClient.exe RefreshSettings @rem. @start ms-settings:windowsupdate
@abbodi1406 shouldn't it be: Code: @wmic service usosvc call StopService @wmic service wuauserv call StopService @del /s /f /q "%ProgramData%\USOShared\Logs\*" @del /f /q "%ProgramData%\USOPrivate\UpdateStore\*" rd /s /q "%ProgramFiles%\UNP" @wmic service wuauserv call StartService @wmic service usosvc call StartService @UsoClient.exe RefreshSettings @rem. @start ms-settings:windowsupdate the output doesn't have failures: Code: C:\Windows\system32>@wmic service usosvc call StopService Executing (\\DESKTOP-EIMQ1BF\ROOT\CIMV2:Win32_Service.Name="UsoSvc")->StopService() Method execution successful. Out Parameters: instance of __PARAMETERS { ReturnValue = 0; }; C:\Windows\system32>wmic service wuauserv call StopService Executing (\\DESKTOP-EIMQ1BF\ROOT\CIMV2:Win32_Service.Name="wuauserv")->StopService() Method execution successful. Out Parameters: instance of __PARAMETERS { ReturnValue = 0; }; C:\Windows\system32>del /s /f /q "%ProgramData%\USOShared\Logs\*" Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.1c0c2799-a5e7-4d67-af70-4ba1bd7fa36d.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.3ba153a2-07e0-4a23-b2f9-7e6990a9f2be.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.3ba153a2-07e0-4a23-b2f9-7e6990a9f2be.2.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.46c165ed-bac2-44e5-96f3-44735f002462.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.59874e8a-28c8-4659-8fc9-3af4c9a21772.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.59874e8a-28c8-4659-8fc9-3af4c9a21772.2.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.7682ddce-1e1b-4fce-af37-4c4c827fc0f9.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.7e8ec2d9-bc35-4c15-abe4-6aa90d2e5f49.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.7e8ec2d9-bc35-4c15-abe4-6aa90d2e5f49.2.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.7e8ec2d9-bc35-4c15-abe4-6aa90d2e5f49.3.etl Deleted file - C:\ProgramData\USOShared\Logs\System\MoUsoCoreWorker.8a2d3e33-bed1-4e74-b08d-bb5b291cf37b.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\NotificationUxBroker.c698b821-28fa-4c97-9b6b-dd344b5e23cd.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\UpdateSessionOrchestration.3d5b61e7-7205-4f7b-bbc2-1ae4b49508ab.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\UpdateSessionOrchestration.bac078c2-3b09-439f-8020-bbcf4f5fc940.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\UpdateSessionOrchestration.da3ca888-b4bc-4fa0-8af7-7d99102eabb6.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.4fa1dde2-502a-47a6-9227-bd26a4a20301.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.5f23ee3d-e71f-42dd-abe0-e156dda59bfc.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.66952405-3695-4136-84f8-2e0aba547632.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.898d7e5a-a9ef-47e5-a4e6-5ec3f49f4ebb.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.c183905c-f4e9-4645-8b77-2e542ae5381f.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.d36bc256-d117-4655-9d7b-d4473afbc3d2.1.etl Deleted file - C:\ProgramData\USOShared\Logs\System\WuProvider.fde35af0-879f-4cc4-9144-c753146c3f8f.1.etl Deleted file - C:\ProgramData\USOShared\Logs\User\NotificationUx.e49fe358-a9d9-46a5-8fca-540a52d0695d.1.etl Deleted file - C:\ProgramData\USOShared\Logs\User\UpdateUx.324922f4-5737-4986-be45-1731a5a7c23c.1.etl Deleted file - C:\ProgramData\USOShared\Logs\User\UpdateUx.74c32054-053a-4632-888a-0724a9ca6236.1.etl Deleted file - C:\ProgramData\USOShared\Logs\User\UpdateUx.85af3ded-24b6-4a19-b4d0-90989111b332.1.etl C:\Windows\system32>@del /f /q "%ProgramData%\USOPrivate\UpdateStore\*" C:\ProgramData\USOPrivate\UpdateStore\store.db The process cannot access the file because it is being used by another process. C:\Windows\system32>rd /s /q "%ProgramFiles%\UNP" The system cannot find the file specified. C:\Windows\system32>@wmic service wuauserv call StartService Executing (\\DESKTOP-EIMQ1BF\ROOT\CIMV2:Win32_Service.Name="wuauserv")->StartService() Method execution successful. Out Parameters: instance of __PARAMETERS { ReturnValue = 10; }; C:\Windows\system32>wmic service usosvc call StartService Executing (\\DESKTOP-EIMQ1BF\ROOT\CIMV2:Win32_Service.Name="UsoSvc")->StartService() Method execution successful. Out Parameters: instance of __PARAMETERS { ReturnValue = 10; }; C:\Windows\system32>UsoClient.exe RefreshSettings C:\Windows\system32>@rem. C:\Windows\system32>@start ms-settings:windowsupdate C:\Windows\system32> but the result is the same.
It's just brute-force cleaning to rebuild WU page cache (not WU database itself) failures are not harmful we could add this one before others Code: powershell -nop -ep bypass -c "Get-WindowsUpdateLog -LogPath %temp%\temp.log -ForceFlush"
Powershell -nop -noni -ep bypass -c "Get-WindowsUpdateLog -LogPath %temp%\temp.log -ForceFlush -Confirm:$False -Verbose" it asked me to confirm so i added Confirm:False & it did its job automatically without user prompt. Before WU "View Updates History" always crashed when i click on it but after running both scripts i can successfully enter into it Thanks a Lot .
yes sure brother why not . before whenever i click on "Virew updates History" systemsettings app always crashed but now it opens like a charm within a second. screenshot of opened "view updates history"
Code: Microsoft Windows [Version 10.0.19044.1266] (c) Microsoft Corporation. All rights reserved. C:\Windows\system32>powershell -nop -ep bypass -c "Get-WindowsUpdateLog -LogPath %temp%\temp.log -ForceFlush" Confirm Are you sure you want to perform this action? Performing the operation "Stopping Update Orchestrator and Windows Update services" on target "DESKTOP-EIMQ1BF". [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y Converting C:\Windows\logs\WindowsUpdate into C:\Users\Tester\AppData\Local\Temp\temp.log ... Directory: C:\Users\Tester\AppData\Local\Temp\WindowsUpdateLog Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 10/12/2021 2:06 AM SymCache Input ---------------- File(s): C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.2.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.3.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.4.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.5.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211011.135505.558.6.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211012.005049.918.1.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211012.005049.918.2.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211012.005049.918.3.etl C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211012.020349.131.1.etl 0.00%5.65%11.31%16.96%22.61%28.27%33.92%39.58%45.23%50.88%56.54%62.19%67.84%73.50%79.15%84.81%90.46%96.11%100.00% Output ---------------- DumpFile: C:\Users\Tester\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00000 The command completed successfully. Input ---------------- File(s): C:\Windows\logs\WindowsUpdate\WindowsUpdate.20211012.020515.968.1.etl 0.00%100.00% Output ---------------- DumpFile: C:\Users\Tester\AppData\Local\Temp\WindowsUpdateLog\wuetl.CSV.tmp.00001 The command completed successfully. WindowsUpdate.log written to C:\Users\Tester\AppData\Local\Temp\temp.log C:\Windows\system32> Same result
@Enthousiast Do you have Windows 11 arm64 LP? mul_windows_11_languages_optional_features_arm64_dvd_ad8a95ae.iso