So what the f*k is going on with the July and August updates. The dudes in tenforums also have the Error 0x800f081f. Is it time to go back to good old Windows 7?
I didn't do ANY cleanups or modifications. Uninstalling UWP apps that Windows itself gives you the option to uninstall should NOT pose a problem. And even if it didn't let you uninstall them, it STILL shouldn't pose a problem.
I have to test if it has the same impact but uupdump uup conversion uses /startcomponentcleanup by default, when updates are applied during the process. The test iso's i made for my latest tests were made manually with no cleanups and all works fine.
The fix worked for me on Polish version of windows. It is quite possible that other language versions such as (drumroll) English Simplified, which @Enthousiast uses, have rollbacked some language resources in .329. Then i won't be able to help you.
UUPdump uses @abbodi1406 his UUP>ISO scripts for conversion and updates integration. My 18362.xxx iso's are bases on the 18362.1 uup dump files, but i run W10UI_x.x for updates integration separately.
The logs says you did (or the system auto-did it via schedule task) C:\Windows\system32\cleanmgr.exe /autoclean /d C:
So, it was like the second test here? https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-446#post-1544574
Bro I HAVE NOT run any clean up and I HAVE disabled the auto clean up task under Task Scheduler > Microsoft > Windows > Servicing. I'm not lying. If anything it was done by itself and I have no idea how. I've formatted 2 times and Im trying to fix the problem, why would I be lying?
No one said you are lying, i just pointed to the fact that a cleanup was performed after further digging, it seems launch by the system Code: 2019-08-31 00:50:58, Info CBS Maint: launch type: Automatic 2019-08-31 00:50:58, Info CBS Maint: begin deep clean
Is there any way to prevent it? As I said I have disabled the task under Task Scheduler > Microsoft > Windows > Servicing but apparently it didn't do anything. Do I have to disable anything else? Some registry tweaks?
Does disabling "Windows Update Cleanup" prevent this problem? Code: reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Update Cleanup" /v "StateFlags6553" /t REG_DWORD /d "0" /f cleanmgr /sagerun:6553
windows10.0-kb4517245-x64.cab is the same here : https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-441#post-1543740 to get 18363.327 https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-444#post-1544292 to get 18363.329
Yes, the 1909 enablement package is the same but doesn't have anything to do with .327 or .329, it ONLY bumps up 18362 to 18363
Does that totally disable it? maybe this? Code: reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Update Cleanup" /v Autorun /t REG_DWORD /d 0 /f however, Update Orchestrator may initiate the cleanup on its own, whatever how that happen
Clean formatted, disabled every auto task possible and maintenance. Still same error. Im fking out, bye. Cya when 20H1 releases.