Recent content by dimpep

Yes, I did that. Everything seems fine. I think I have a corruption in the AppX base. That's what I will try to solve.

AI cannot help me unfortunately. It seems to be a generic issue. See here: Error is 0x800f0920

So, I managed to restore a backup with macrium, where the component store is not corrupted. I've tried to install the june cu but again the exact same behaviour, it halts at 97%. It fails to register the update from staged to completed. I think I'm doomed! Unfortunately, repair install via...

It depends. Iso should be the same exact install language and equal or larger build number. And even then, sometimes doesn't work. The setup engine should be larger than the windows build number. I faced this problem multiple times

For sure! I've created the usb flash drive using either Rufus or mct

Yes, normal iso from mct. I will test with one source only. Chat gpt gave me this command. In the wim the files are supposed to be there but they cannot be restorrs My windows version is not Gr, is en-us from the installation

Installation assistant says I already have the latest update of windows.

No I don't. I use the option for repair install with no luck. The servicing mechanism is pretty bad condition maybe and it didn't work. I don't have high hopes for the assistant but I will try

Not available unfortunately. It fails. Now Ι'm stuck at 26200.8246

I want a repair install. Dism /Online /Cleanup-Image /RestoreHealth finishes with components not found and a failure code. The log says (via AI of course) that the components are deprecated. I've tried offline dism with two images at once...

In Panther logs, it says HostSystemisNewer and somewhere there it says that the host system is 26200 and the target system is 26100. All of these I have found with AI.

Everything is correct. Language, version and higher build number. But unfortunately as I found out, up to now, all 26200 builds are based on 26100 setup engine and when I'm trying to in-place upgrade the system finds that I'm actually downgrading. This happens because 26200 is a disguised 26100...

Did this, multiple times. Repair failed even when I use external source.

Thanks for the answer. Did all of these a lot of times. Every time "keep nothing" is the only option. And searching with AI found that the install engine of both 26200 and 26100 is 26100 based and windows thinks I'm downgrading from 26200

Hey, I'm trying to repair install my windows 11 26200 25H2 but I cannot, all isos, from uupdump and windows insider (i'm in release preview channel) for 25H2 are indeed 26100 because it share the same undelying setup machine. I tried to spoof registry with 26100 but it didn't work. Setup tells...