JFX

Well your Dism crashes cause there is no downlevel version of api-ms-win-core-libraryloader-l1-2-0.dll. The native (\Windows\System32\api-ms-win-core-libraryloader-l1-2-0.dll) one can't be used. So with one of the big updates dism was linked against this new library, however MS forgot to compile a downlevel version. Well this is something that have to wait til next year Properly the best solution will be to rely on ADK DISM. Well, that's just prime! So it was wimgapi.dll which wants to load that file. Fixing one rare occurring problem to rise an regular occurring one.

Oh, so let me guess you try installing one of the updated Win8.1 update 1, 2 or 3? And inside that new image there is no api-ms-win-core-libraryloader-l1-2-0.dll inside \Windows\System32\downlevel? But for sure there is one in \Windows\System32

Dism is one hell of a buggy software, all these error's would be crashing if the nice MS guy would do some error handling. Sadly I can't reproduce it, best would if you sent me a sysinternals process monitor log file.

Yes, on Windows 7 Host you'll need the aps-ms-win*.dll next to the wim or in the api-set folder. This is necessary to get the dism.exe from win8.1 or later running. If you running a Win8.1 system, they are not needed. The Vista driver integration should now work. There was a problem with pkgmgr command line. Also it behaves different than dism, if one specific a drive letter instead a folder path for drivers.

A versions mismatch should not make a problem here. Is this a mounted ISO or a stand alone WIM, With a normal ISO the \sources\api-ms-win-downlevel-*.dll files will be used for driver integration for Win8.1 out of win7. If not they have to be in the "api-set" folder inside winntsetups tools folder. Anyway try Beta2 It should fix at least the Vista and one Dism related problem.

Properly, I usually stay with one architecture, so I overseen this would happen. Tomoorw I check what happens with Vista, than it's about time for new beta

So, dism crashes cause there is no wimgapi.dll in \Windows\Syswow64 folder. Well this can be fixed quite easy. But for Vista, my last idea to use dism was wrong, it's not possible to use dism here for driver integration.

Driver ingratiation for Vista is a special one, as there is no dism on vista. Also I never tried WinPESE WOW64 for that Vista servicing. In next version I'll try to use DISM from current system.

Well, it's not that easy to explain how to get the offsets. But for your bootres.dll, seems it's also in bootmgr.exe, at offset 0x575C.

Well, you could check the Winntsetup.log in the windows directory. It should show which *.inf files were integrated and which not. Also there should be a Dism_stdout.log, too.

Yeah, better let's wait for Win10 final Well, bmzip.exe does compress better, so the new bootmgr will be slighlty smaller. I use the same compression code MS uses, so the size will stay more or less equal. Maybe next year I'll add "ABC" feature. This should be the offsets for 6.3.9600.16415 0000CF0E: 0F 900000CF0F: 88 900000CF10: AE 900000CF11: 02 900000CF12: 00 900000CF13: 00 90000194A9: 74 EB000194D3: 75 EB At address D84 you have the \Boot\BCD string that you can change.

congnt92, please re-download and try again. http://1drv.ms/1plzVcu

@Atari800XL WinNTSetup, does not change the drive letter, it just tells the Windows to do it. But Vista ignores this in the fast install way, so it will always stay with the drive letter it was installed. @Steve6375 Thanks for the dir command, this /aL switch it's quite useful. But /NoRpFix is only for junctions that point outside the image.

"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.