Recent content by hader

(Maybe is is a good idea to use the original 25H2 v2 ISO (full official version from MS) with build 26200.8037. Then update everything to 8655 and then update your system to 9168.) I checked my ComponentStore (9168) and there is absolutely nothing wrong with it. There is no issue with...

I get your hesitation but this is the only way to get rid of this problem. SFC checks other things. RestoreHealth is doing it's job for 95%. That leaves only 5% that can not be fixed. I had 2 incidents with this in the past, tried everything. Also In-Place-Installments. Nothing worked. A new...

DISM is not "broken". It still does it's job. The only thing is; that it is downloading 2x 256Mb (2nd is a retry that fails) when nothing is wrong all the time. I explained it already in thread #243. When something is wrong; it still repairs. I saw this for myself after an previous update was...

Yes I know. /RestoreHealth is not broken. But how long did it take? On my system this command went from 4 minutes to 14 minutes because of that CBS-engine bug introduced with 8655.

Hi Garlin. I am curious. Which script did you used to get this? I ran "Check-BootMedia.bat" from your v2026.08.11 toolkit and I got not such a conclusion. I mounted a MCT ISO build 26200.9168 on N. Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved. Secure Boot: ON...

3 Times? Never have seen that before. If an In-Place-Installment did not solve the issue then a fresh Install is in order. About In-Place-Installment; Parts of the registry is left alone otherwise it doesn't remember all your personal data. I suspect that only some parts are refreshed in the...

It does not matter if you format things. With format you just reformat your drive to make sure that no corrupted sectors are left. You have to format your disk once. Once you bought a disk. They are already lowlevel formatted but despite this it is a good thing to do. And then you are most...

Yeah. That means: In-Place-Installment! The issue can not be fixed by this way. Just mount the MCT ISO and execute setup.exe. It already knows you are doing an In-Place-Installment without touching your data. Have done this many time when I had things that I could not resolve. Once I created a...

Can you repeat this without the index; ':6'? It is not needed with this command. If the .ISO matched your build it should contain the version you have; Home, Pro etc. I use this index only if I want to know something about the build of an ISO; Dism /Get-WimInfo /WimFile:G:\Sources\install.esd...

OK. I must confess. I am a technerd. 🤔 :geek: :p I talked to ChatGTP about this CBS-bug inside 8655 and onwards. Got some surprising insight about the issue: (Was always wondering why RestoreHealth made 2 attempts to download 256Mb. 1st: 256Mb. 2nd: 0 Bytes...) I now see why that second...

It looks that something is not correct with your Windows system. Make sure to run SFC /scannow. There may be error that can be fixed with SFC. I tried the same with my system; 1 - DISM /online /cleanup-image /RestoreHealth -> Completed with no errors. 2 - DISM /Online /Cleanup-Image...

Just what I said....

Ok, Thanks.👍That is sufficient information for me. I can just go to this page; Ibra86's Pastebin - Pastebin.com and check if a new line is added to this list. Then I know if I can start the MCT in order to get that build version. I rather use this official method then getting it from an other...

That's strange. I used MCT some time ago I got: 26200.8653. Official was 8655. (Including the CBS-bug that is still not resolved) The next time; (Did not know that around 1-2 August they corrected it to 8875) I got 8873 (17-July) did a In-place-installment (same day) with this one. By the time...

I think you are missing the point here. It's only affects newer downloaded scripts since 26200.8168. Did you download this script with 26200.9168 and ran that script? Older scripts that are downloaded before 26200.9168 are not affected; they are not marked! Now they are because Windows with...