kiler129
New member
- Jul 31, 2023
- 2
Hi all!
The main symptom is the cumulative update refuses to install. I think I tried every magical trick in the book I know involving dism and other tools, including nuking WU resources. Sadly, I didn't get far.
1. SFC: no corruptions found
2. DISM
I tried looking at the CBS file but I don't understand why the WU cannot find these missing packages and fix manifests. In addition, I wonder how WU, given the claimed CBS atomicity can end up in such a broken state due to (presumably) botched update install
Thank you in advance for help. I would love to avoid reinstalling that instance, as a lot of settings were changed and there isn't really a documentation for it.
The main symptom is the cumulative update refuses to install. I think I tried every magical trick in the book I know involving dism and other tools, including nuking WU resources. Sadly, I didn't get far.
1. SFC: no corruptions found
2. DISM
- /CheckHealth detects corruption
- /RestoreHealth is unable to restore the component store. The log shows A LOT of missing manifests, unusually large number I would say. I attached the DISM and CBS logs. I reset them before doing the restore to only capture one session without all noise.
- I tried using the /Source with an ISO. However, but LTSC ISO isn't available for that build (19044.2846), but only for the older ones (19041.844). I don't think MS even has a pre-built iso for that according to files.rg-adguard.net.
I tried looking at the CBS file but I don't understand why the WU cannot find these missing packages and fix manifests. In addition, I wonder how WU, given the claimed CBS atomicity can end up in such a broken state due to (presumably) botched update install
Thank you in advance for help. I would love to avoid reinstalling that instance, as a lot of settings were changed and there isn't really a documentation for it.
