JFX

"Unsupported OS, newer ntdll.dll needed!" Means your running this tool not under Windows 8, and your ntdll.dll has not the functions to decompress and recompress bootmgr.You can put ntdll.dll from a win8 install next to the program an try again. If the offset has changed, then please don't change these bytes.If I have some time I take a look at the new version.But seriously you don't need a win10 bootmgr, do you?

Yes, you will need to make a normal install before, with original setup.exe or you boot from the DVD / ISO. This usually results in a system drive C:. This installation sysprep, generalize and capture. The new WIM can be used with WinNTSetup and will always have C: as letter.

No, there has nothing changed til now. I could replace all D:\ strings in the registry, but I guess there are also xml and some binary files. Just do a normal install once and make a new sysprep image.

@kreker Bootice can't create a "Recovery image" partition. But It can create a GPT partition scheme with ESP and MSR. You have to use diskpart, to set the right ID to the recovery partition. @mariella That actually strange because I just use IsProcessorFeaturePresent API to determine if the CPU has PAE, NX and SSE2 for Windows 8 installs. And the Win8.1 x64 required CX16 and LAHF are also very easy to receive. Not sure whats going wrong, but you can simply ignore this warning.

Hmm, can you post the output of Sysinternals Coreinfo Coreinfo.exe -f

Hi mariella, For the ISO mounting yes imdisk have to be installed. Does it help if you move WinNTSetup_iso.cmd from the tools folder next to the WinNTSetup_x86.exe? The red icon should have a tooltip if you hover the mouse a while. It's properly the CPU check, that telling the current machine doesn't support this OS.

Thanks for the update kreker, 1) A single NTFS partiton would be enough for wimboot, but the size is a good question. With every upate you install your wimboot installation grow more, cause the obsolete files in the wim can't be deleted.. Depending on your usage and hibernate and page file size, I would say at least 25 GB. Keep in mind that you have to place the install.wim on an NTFS drive before using WinNTSetup. Also it have to be a install.wim not install.esd nor install.swm. 2) Disable security warning for downloaded files is the following reg tweak Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Attachments] "SaveZoneInformation"=dword:00000001

@josywong It doesn't look easy to find out what edition is supported by oem:dm. I guess the original setup is checking if the product key in the MSDM table matches an edition in the wim. No sure if I can implement something like that.

A new Beta version is available with many fixes and I also added the new Win10 Taskbar tweak. For wimlib users, please make sure your use latest version 1.7.3

What check do you mean, a mark in the top right like the it's currently for SLP1 and SPL2?

@simplex It should be fixed now.

Hi Maanu, nice to hear from my friend, I'm glad to hear you doing well. There isn't actually much WinNTSetup does for EFI. Just 1 command BCDBoot.exe C:\Windows /s S: / f ALL, where S: is the EFI partiton A read Icon for EFI PART means the partition does not have the EFI SYSTEM partition GUID. So a strict uEFI should not accept this partition.

This is not a standard windows setup, these are upgrade images thought to be used with windows update.

Hmm, I don't really think decrypting on the fly would make much sense. Making changes to the source isn't something I like. However, you can ask synchronicity, what he thinks about adding that decrypting code to wimlib.

An even more simple way to explain? Well, I give it a try: IT IS NOT POSSIBLE!!! You simply can NOT hibernate a system that was booted from a VHD.

Devdevadev I just mean you should use VHD instead of VHDX. For the hibernate, it's a limitation of VHD booting, there is nothing I could do about.

I don't now about sleep but hibernate is not supported in nativeVHD boot environment. WinNTSetup will disable hibernate only, if you tell it to do. If you disable pagefile.sys and have not enough RAM, than you will get an error message by windows if you reach your RAM limit. BTW: Why do you use VHDX, you know they require more size, do you?

You don't need to fix MBR and PBR, they will be updated by default. The Only thing you need to take care is the BOOTFLAG But your's is green so everything is okay.

@devdevadev Advanced users, not advanced features. You right, the Technical Preview version wasn't recognized for Wimboot usage. It's wired how MS uses version numbers these days, they skip some and forgot some others completly. So re-download and try wimboot now.

It's an optional feature, for advanced users, and they can usually download the right files. The 2nd is the right zip for you.

Well I didn't change much, just some smaller fixes I noticed the last weeks. Also added compatibility setting to the app manifest so it will not run in compatibility mode of Windows 8.1. What I thing about Windows 10? I guess I'm dissapointed like everyone. It looks just like a tiny update to the current Windows 8.1 and by no means something that worth of skipping a version number. First fate took my Opera now it takes even my OS, what next? Seems I will use Windows 7 until very end, maybe even after 2020 But at least the new wimgapi has a new feature to add files ...

I made small fixes for Windows 10. Please report if you find anything that's not right.

Updated to version 2.0 - removed ia64 architecture - reduced download size - changed folder layout according to ADK install - added command line options: -xpramboot, -xpwimboot -7z:{pathto7z.exe}

Hi Agent47, You have 3 options to add mass storage drivers for XP install. 1. choose an already slip-streamed source made with Driverpack Base tool (both integration options should work) 2. choose the drivers "Add Drivers" option 3. integrate with "Run Driverpack Base" option, it let's you run the Driverpack Base tool after coping the source files

@sixcentgeorge Sorry for the delay. The GUI should be easy to understand and I don't want it to confuse average users with to many options. Not sure what you mean with grub4dos here?