This will ensure that it does not attempt a repair during the upgrade process. If you use Automatic Client Remediation, add the following registry key in your in-place upgrade task sequence to change its behavior to Notify Only. Press Win+R, type in: regedit.exe and press OK.
Windows 10 setup exe auto delete free#
The Settings app includes Storage sense, a feature that runs automatically when running low on storage to free up space. STEP 6: Clear the Windows registry from WINDOWS 10.EXE virus. On Windows 10, you can use Command Prompt and Task Scheduler to automatically delete files older than a certain number of days to free up space and keep your files organized. Delete any task related to WINDOWS 10.EXE. This feature obviously does not care if anything else is running and just happened to trigger during the upgrade and broke the task sequence execution. STEP 5: After that press Win+R, type in: taskschd.msc and press OK to open Windows Task Scheduler. The red text shows us it is an Automatic Client Remediation repair. If we look at the ccmsetup.log to see what triggered that, the command line gives us the clue:Ĭcmsetup command line: “C:\WINDOWS\ccmsetup\cache\ccmsetup.exe” /remediate:client /log:”C:\Windows\CCM\logs\repair-msi-B7D3A842-E826-4542-B39B-1D883264B279.log” The red text above is where things go wrong, the SCCM client starts to re-install itself during the in-place upgrade. 10:02:28 AM – (ccmsetup.log) CCM setup complete 10:02:24 AM – (ccmsetup.log) CCM setup starts services 10:02:11 AM – (ccmsetup.log) CCM setup starts installing services 10:01:12 AM – (ccmsetup.log) CCM setup starts copying new files and registering components 10:00:22 AM – (smsts.log) Windows 1709 upgrade error starting CCMExec service. WMI error 0x8004108A (User attempted to register a provider instance but the COM server for the provider instance was unloaded) 10:00:21 AM – (smsts.log) Windows 1709 upgrade error compiling SCCM policy to WMI. 10:00:20 AM – (smsts.log) Windows 1709 upgrade starts task sequence initialization to resume upgrade process 09:59:xx AM – (ccmsetup.log) CCM setup starts a re-install of 1802 client, stopping CCMExec and un-registering components 09:41:xx AM – (smsts.log) Windows 1709 upgrade Windows setup.exe completes and initiates reboot of system to complete upgrade 09:20:xx AM – (execmgr.log) Windows 1709 upgrade TS started The OS had upgraded successfully to 1709 and SetupDiag also reported all was well in that area, however the remainder of the task sequence never ran, not a single-step post the upgrade task, so the device was missing some post-setup customisations.Īnalysing the SCCM client logs on the local machine this is what I saw: I ran into an issue the other day during a W10 1703 to 1709 in-place upgrade where the upgrade task sequence bombed after Windows setup had completed.