I think it's simpler than your deduction. I used Windows 10 and Windows 7 without any conflict. I just replaced Windows 10 by Windows 11. To boot on Windows 7 or 11 I use F8 and the BIOS menu. I think the Windows 10 Explorer in WinPE10 is incompatible with Windows 11. Thank you I will keep my configuration current because I have no problem to save or restore with WinPE10 SE The only problem I can not watch the Windows 11 disc.
You could also try using the script v1.7 OPTION 2 usb but set to NTFS so that it installs with MBR instead of GPT partitioning. Run setup with the legacy CSR on your system so that it doesn't use UEFI booting and it might be able to see your drive cross install. It's a long-shot, but it might work.
Brother It seems theres a issue from ISP Network Drop thatswhy your comment is two times written inspite of one . as both are same.
Brother its not my Forum i am just a user with no knowledge or we may say a Novoice in Computing Only Staff : Admin or Moderator can delete one now n nobody else
Back into Enterprise IT for me and the big change is cloud everything. Microsoft 365 is huge. Google One and AWS are also very prominent. No one runs email servers anymore. File and domain services are duplicated and backed up into Onedrive and Azure.. Cloud PC is in that same direction where everything else has gone already.
Your partition is not invisible. It just lacks a drive letter Just launch the disk manager, right click on the affected partition, select change drive letter (or whatever is spelled in English) and add the letter you like.
Yea more or less what I want as well No I think I missed that one, was a custom build, I guess? I used either Thin PC or my own built WES7/8 images. Perhaps not sure if people are aware of that but ThinPC is still receiving the updates as todyay, no hack involved.
Never tested it I was about to download whats supposedly needed but the 8GB download scared me a bit.
The registry hack that works for the previous Build doesn't work for this particular one though. Perhaps, the registry name and value have been changed to something else by Microsoft
Hello; It did not come to the idea.First times that it happens to me. I reversed SSDW7 (C) with SSD128 on WinPE10 SE best regard
It happens on some configurations... native vhds, mixed MBR/GUID configurations and so on... Whatever glad my suggestion was the correct one and helped.
p.s. ESD = high compressed WIM You cannot combine same edition for two different languages, that's not how multilingual Windows works move pro_en-us.esd from download folder, then create Pro UK english
Thanks for confirming that. I wasn't trying to create a Multilanguage ISO, just a separate US and UK version. I tried removing the pro en-us .esd and was then able to successfully create a Pro UK ISO. I suppose I naively assumed that the script would only use the required files from the downloaded UUPs folder, so it wouldn't matter if the pro en-us.esd file was still present. We live and learn. Thanks again.
A word of warning: In dual boot configurations, the disk or partition holding the other OS is hidden for a reason. Ownership. It's a minefield. E.g. if you're in Windows 10 and you want to get something from the My Documents folder (or some other system folder) on the Windows 7 partition, Windows will tell you that you do not have permission to access that folder, and will helpfully suggest to "click here to permanently take ownership of the folder". If you do that, Windows 7 will not boot, or will boot with a whole bunch of errors. Much better to have a non system folder that both OSs can see, and use that to share files between them.