So you have wim. What is the issue just use wimlib & restore the wim itself to any drive, without using any propriety tools?
=================== UPDATED Initialpost! ===================== Hey, I wasnt aware of wimlib. Appreciated. I applied the WIM file to an empty SSD via SATA-2-USB adapter, using "wimapply.bat" from within a Windows 11. It instantly started creating all the files&folders on the SSD, which took about 20 minutes. Followed by a longer process "extracting file data" (21 gigabyte), which almost took 2 hours. Probably related to the old Laptop and no USB 3.x. Followed by the process "Applying metadata", which took another 20 minutes. The cmd ended with 2 times "Command %) wrong or not found" but it said "Done applying WIM image." before. Next time Ill do it on a faster PC. I had a ready to go SSD with all windows folders on it then. As there was no EFI partition on the SSD yet, the wimlib site says I have to use boot files / BCD, before beeing able to finally boot it from inside a PC/Laptop. The SSD attached via SATA2USB Adapter is "E:". Will adding "bcdboot E:\Windows /s E:" do the job? (even if its not C) Also Im on Windows 11 (x64)
Today I installed Windows 10 Teams on a: "hp compaq pro 6200 microtower" i3-2120, 4GB RAM, 120GB SSD using a GeForce 210 instead of the onboard graphics HD2000. I dont understand on how I would use tsforge/massgravel on "Windows Teams" as I cant use powershell I can open a CMD prompt using rightclick on the windows icon though and run masgravel. It does activate the already activated Windows Teams, but cant find Office when selecting tsforge and/or Ohook. It would be Office 365. Also forcing the nvidia drivers to work would be the next big problem I guess. p.s. Why would the Windows installation still be called "pre-release" 19041.VB_RELEASE.191206-1406? Would there be any "final" "Windows Teams" ISO out there?