Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

  • Country


Posts posted by devdevadev

  1. Hi JFX...

    @JFX @jaclaz @wimb @alacran 


    "%wpath%\WinNTSetup%pp%.exe" VHD-CREATE -file:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.vhd" -size:15GB -type:expandable -label:"Win10x64-WB" set e=%errorlevel% set "ALPHABET=_ABCDEFGHIJKLMNOPQRSTUVWZYZ" call set VHD_DRIVE=%%ALPHABET:~%e%,1%% if "%VHD_DRIVE%"=="" echo ERROR! if "%VHD_DRIVE%"=="_" echo ERROR! echo Win10x64-WB.vhd is mounted as %VHD_DRIVE% "%wpath%\WinNTSetup%pp%.exe" NT6 -source:"%isopath%" -wimindex:"2" -syspart:%SYSPART% -tempdrive:%VHD_DRIVE% -unattend:"%XML%" -drivers:"%E2BDRIVE%\SVBus" -Sysletter:C -RunAfter:"COPY_VHD_WIMBOOT_FILES.cmd %E2BDRIVE% %VHD_DRIVE% %OSPART%" -setup -reboot -testSigning



    I use following command to Capture Win10x64-WB.vhd to Win10x64-WB.wim in WIMBOOT mode.

    wimlib-imagex.exe capture %VHD_DRIVE% C:\WIMBOOT\W10x64-WB.wim    --config=%E2BDRIVE%\VHD_WIMBOOT\WimBootCompress-2019-03-31.ini --include-integrity  --wimboot  --compress=LZX --threads=4


    Applying WIM to VHD in WIMBoot mode-

    Currently I use following command to Apply WIMBooted Win10x64-WB.wim to 1.5 GB Win10x64-WB.vhd in WIMBOOT mode.

    wimlib-imagex.exe apply C:\WIMBOOT\W10x64-WB.wim %VHD_DRIVE% --wimboot

    What exactly WinNTSetup command I should use that will be equivalent to above wimlib-images apply command in WIMBOOT mode ?



  2. 21 hours ago, JFX said:

    - cmdline VHD-CREATE and VHD-ATTACH return errorlevel for driveletter

    Thanks a lots for this very useful feature....AFAIU we will use this feature in command line as follows -

    "%wpath%\WinNTSetup%pp%.exe" VHD-CREATE -file:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.vhd" -size:15GB -type:expandable -label:"Win10x64-WB"
    set e=%errorlevel%
    call set VHD_DRIVE=%%ALPHABET:~%e%,1%%
    if "%VHD_DRIVE%"=="" echo ERROR!
    if "%VHD_DRIVE%"=="_" echo ERROR!
    echo Win10x64-WB.vhd is mounted as %VHD_DRIVE%
    "%wpath%\WinNTSetup%pp%.exe" NT6 -source:"%isopath%" -wimindex:"2" -syspart:%SYSPART% -tempdrive:%VHD_DRIVE% -unattend:"%XML%" -drivers:"%E2BDRIVE%\SVBus" -Sysletter:C -RunAfter:"COPY_VHD_WIMBOOT_FILES.cmd %E2BDRIVE% %VHD_DRIVE% %OSPART%" -setup -reboot -testSigning

    Is this correct use of this feature ? Any better IDEA please ?

    When we use WinNTSetup tool then- syspart: is automatically detected and assigned. Is there any way in WinNTSetup command line so that we can also get -syspart: as any variable/errorlevel ?


    I use following command to Capture Win10x64-WB.vhd to Win10x64-WB.wim in WIMBOOT mode.

    wimlib-imagex.exe capture %VHD_DRIVE% C:\WIMBOOT\W10x64-WB.wim    --config=%E2BDRIVE%\VHD_WIMBOOT\WimBootCompress-2019-03-31.ini --include-integrity  --wimboot  --compress=LZX --threads=4

    What exactly WinNTSetup command I should use that will be equivalent to following wimlib-images apply command in WIMBOOT mode ?

    wimlib-imagex.exe apply C:\WIMBOOT\W10x64-WB.wim %VHD_DRIVE% --wimboot

    @JFX @jaclaz Can anybody please help regarding this issue ?

  3. I use following command to Capture Win10x64-WB.vhd to Win10x64-WB.wim in WIMBOOT mode.

    wimlib-imagex.exe capture %VHD_DRIVE% C:\WIMBOOT\W10x64-WB.wim    --config=%E2BDRIVE%\VHD_WIMBOOT\WimBootCompress-2019-03-31.ini --include-integrity  --wimboot  --compress=LZX --threads=4

    What exactly WinNTSetup command I should use that will be equivalent to following wimlib-images apply command in WIMBOOT mode ?

    wimlib-imagex.exe apply C:\WIMBOOT\W10x64-WB.wim %VHD_DRIVE% --wimboot

  4. You are right Sir...I am running command within from a batch in 'boot.wim' environment but I want to inject VHD_WIMBOOT.cmd file within "%VHD_DRIVE%\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp" folder which will be created after the Copying Phase of WinNTSetup Installation. It's why I need to use /Runafter so that I can inject .cmd files within VHD just before reboot ? Is there any better way which I should use here ?

    Are you talking about using following approach ?


    @echo off
    copy "%1\VHD_WIMBOOT\SWITCH_DEFAULT_OS.cmd" "%2\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp"
     copy "%1\VHD_WIMBOOT\VHD_WIMBOOT.cmd" "%3\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp"

  5. -RunAfter:"copy "%E2BDRIVE%\VHD_WIMBOOT\SWITCH_DEFAULT_OS.cmd" "%VHD_DRIVE%\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp" & copy "%E2BDRIVE%\VHD_WIMBOOT\VHD_WIMBOOT.cmd" "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp" "

    Can I use two commands within -RunAfter switch as above ?

    Is it valid ?

  6. 20 minutes ago, JFX said:

    I said, that I add an exitcode, so just wait a day or so for the next version.
    If you can't wait try figure out the command line yourself ...

    Sorry to disturb you Sir...I could not understood the meaning of exitcode actually...Thanks for your kind help and support....BTW, I just loved the new Dark Theme mode in WinNTSetup. 

  7. When we create VHD using WinNTSetup Tool then it automatically attach VHD and use a random free Drive Letter to mount VHD and automatically set that drive letter of VHD as installation drive. Is there any specific protocol that decide what Drive Letter will be used for mounting VHD ?

    "%path%\WinNTSetup%pp%.exe" VHD-CREATE -file:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.vhd" -size:1536MB -type:expandable -label:"Win10x64-WB"

    It will be nice if VHD-CREATE  provide an option to use desired Drive Letter for attaching created VHD. OR you can set a variable VHD_,DRIVE containing the drive letter of attached VHD. So that we can use %VHD_DRIVE% as Installation drive.


  8. Hi JFX....

    "%path%\WinNTSetup%pp%.exe" VHD-CREATE -file:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.vhd" -size:1536MB -type:expandable -label:"Win10x64-WB"

    "%path%\WinNTSetup%pp%.exe" VHD-ATTACH -file:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.vhd"

    How I can get Drive Letter of just mounted VHD so that use as %VHD_DRIVE% in following command to install Windows in VHD using WinNTSetup command line.

    "%path%\WinNTSetup%pp%.exe" NT6 -source:"%FREEDRIVE%\WIMBOOT\Win10x64-WB.wim" -wimindex:"1" -syspart:%SYSPART% -tempdrive:%VHD_DRIVE% -Sysletter:C -WIMBoot -compact:lzx -wimlib -wbc:wimbootcompressed.ini -setup -reboot -testSigning


  9. Thanks JFX for providing your precious time...

    t's looking WinPE already assign drive letter to Boot Partition (System Reserved). So how I can automatically detect and get Drive Letter of 'Boot Partition' (System Reserved) using cmd in exactly the same way WinNTSetup do ?

    Please help me to automatically get Drive Letter of 'Boot Partition' (System Reserved) using cmd with WinNTSetup approach if possible...

    Thanks & Regards...

  10. Should I use following code in order to make automatic Dual boot of Win 7 and Win 10 ?

    if exist %SYSPART% format %SYSPART% /Q /Y /V:"Windows 7"
    %WinNTSetup% NT6 -source:%PTN2%\sources\install.esd -WimIndex:2 -syspart:%SYSPART% -tempdrive:%SYSPART% -unattend:"%XML%"-ForceUnsigned -drivers:"%PTN2%\driver_Win7x86" -Sysletter:C -RunAfter:"set_7_usb_boot.cmd C:\windows" -OEM:%PTN2%\sources -setup -reboot
    if exist %SYSPART1% format %SYSPART1% /Q /Y /V:"Windows 10"
    %WinNTSetup% NT6 -source:%PTN2%\sources\install.esd -WimIndex:6 -syspart:%SYSPART% -tempdrive:%SYSPART1% -unattend:"%XML%"-Sysletter:C -OEM:%PTN2%\sources -setup -reboot
    goto :EOF

    I think after restart 'Win 10' will continue remaining installation phases till preparing the desktop. After reaching at the desktop of 'Win 10', I will have to auto boot to 'Win 7' entry in order to complete remaining installation phases of 'Win 7'. 

    So how I can set to auto boot to a particular BCD *(Win 7) entry after auto-restart of 'Win 10' ? Is there any command line way to auto boot to a BCD entry after restart ?

    bcdedit /default {Windows 7 identifier}

    OR May be after reaching at the desktop of 'Win 10', I should set 'Win 7' boot entry as default OS using command line and then just restart to auto continue remaining installation phases of 'Win 7' ?Suppose I have Dual boot of 'Win 7' and 'Win 10'. And I am booted to 'Win 10' desktop. So how can I automatically get  'Windows 7 identifier' using command line ? So that I can make 'Windows 7' as default OS. And then just restart to continue remaining installation phases of 'Win 7'...??

    How 'WinNTSetup' automatically detect 'syspart' drive if exist and assign BootDest=Z: (while in Disk Mgmt there is no drive letter set for 'System Reserved'partition ?). I also want to set BootDest=Z: if 'System Reserved' partition exist otherwise I will use BootDest=%OSPart1%

    How 'Search...' button dialog box is different from normal File Explorer ? How WinNTSetup can see 'System Reserved' partition as Z: while normal File Explorer and Disk Mgmt have not assigned any drive letter to 'System Reserved' partition ? What is secret trick you have used here ? Please help me to understood this concept ...

  11. Hi...JFX

    I want to run a 'WinNTSetup' script within from WinPE10 which will install 'Win 7' to %SYSPART% partition and 'Win 10' to %SYSPART1% one after another without booting to WinPE again. I mean I want to autorun 'AutoDualBoot.cmd' so that it will make complete Dual Boot of 'Windows 7' and 'Windows 10' without any furthe user action !!!

    Is it possible using WinNTSetup command line ?

    Does 'WinNTSetup' support installing two OSes in two different partitions of a Disk one after another without booting to WinPE again ?

    Can I make automatic Dual Boot of 'Win 7' and 'Win 10' using 'WinNTSetup' based batch file ?


  12. What do you marketing guys think about 1.0 release date?

    Should it be before or after July 29? 

    I will prefer 29 to have giveaway of rocking SIB++..............:lol


    Can I expect.........Plz


    Thanks in Advance

  13. Try to read from post #31 down.

    OMG, It was Univeral Watermark Disabler which causes crashing.........Thanks for Tip...Now It's works perfectly....


    Can you please allow us to enable Bottom Left Corner to open 'Start Screen'. I think there should be an alternatively of 'Ctrl+Win Key' for Mouse/TouchPad users similar to SIB+.


    Thanks & Regards...

  14. First Million of Thanks and Regards for 'StartIsBack++' and your Hard Work.....


    It will be better if you also allow us to choose between 'StartScreenIsBack' and 'Win 10 Start Menu' along side your 'StartIsBack++'. By this way we can enjoy best of all Start Menus with the help of your awesome tool. And we can use either of following combination according to our mood. 


    1- 'StartIsBack++' and 'StartScreenIsBack'

    2- 'StartIsBack++' and 'Win 10 Start Menu'


    Thanks in Advance

    • Upvote 1
  15. Hi..


    I had successfully tested both 'WTG + VHDX' and 'WTG + WIMBoot + VHDX' configuration of 'Win 8.1 U1' by using 'WinNTSetup'. It works perfectly. But I could not test it for 'Win 8.1 U3' till now.


    Can anybody plz also confirm both 'WTG + VHDX' and 'WTG + WIMBoot + VHDX' configuration for 'Win 8.1 U3' ?


    But It's looking that either of the above configuration is not working for 'Windows 10' till now........? 



  16. So I guess nobody used this new converted esd with WinNTSetup. Oh well, I still loved the fact that I could use it with WinNTSetup...


    Hi 'JFX'


    I have downloaded '9860.0.141008-2044.fbl_release_clientpro_ret_x86fre_en-us_4268ed97873110ab801beb19b3f5016090623c7c.esd' from MS Server and then Decrypted with esd-decrypter-v4c. After that create Complete ISO with boot.wim and complete 2,5gb install.wim file.


    It's looking that something is wrong with 'WinNTSetup v.3.7.2' because it does not allow me to create 'WIMBoot' of 'Windows 10 Build 9860' while It successfully work if I install 'Windows 10 Build 9860' to either Hard Disk or Virtual Hard Disk (VHD). But when I choose 'WIMBoot' option then every time It give following error while 'WIMBoot' was working perfect in 'Windows 10 Build 9841' .


    Error Code: 0xc0000001 


    Please help me....Why I got above error whenever I choose 'WIMBoot' ?



  17. OK...'JFX'


    Sorry for disturbing you too much..........




    As you said earlier that 'Hibernate' does not work if booting from 'Microsoft Native VHD'. But what if we boot Windows within from 'Raw Hard Disk Image' or 'Raw Partition Image' either via 'EasyBCD NeoSmart Bootloader' or 'Grub4dos' ?


    Can you please tell me how to create 'Raw Hard Disk Image' and 'Raw Partition Image'. I don't know about how to create these Raw Images. Actually till now I was using either your 'WinNTSetup v3.7' or 'Bootice v1.33' in order to create VHD Images but none of them allow to create Raw Images........


    So please suggest me a good tool/method in order to create 'Raw Hard Disk Image' and 'Raw Partition Image'.


    Sorry once again for my stupid questions......


    Thanks in Advance....

  18. http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Windows/Windows_7/A_8951-Boot-from-VHD.html


    Following Point is described in above Site under Tips, Gotchas, and FYIs-

    In case of VHD booting Hibernation is disabled, so you cannot hibernate your laptop.  However, if you expect to be in one given install regularly, you may be able to hibernate by placing that installation directly on the hard drive and putting subsequent alternate installations in VHDs.


    I could not properly understand exact meaning of above para. Can you please explain above para in more simple way....


    Could above point may be useful in my case ?



  19. What may be the reason behind disabling 'Hibernate' if booting from native VHD by Windows ?


    I think 'WinNTSetup v3.7' should show 'Enable Hibernate' checkbox under 'Tweaks' instead of 'Disable Hibernate' checkbox. So that we can 'Enable Hibernate' if booting is performed from VHD by Windows. Otherwise there is no meaning of 'Disable Hibernate' checkbox if booting is going to be performed from native VHD by Windows.


    If possible then please replace 'Disable Hibernate' checkbox with 'Enable Hibernate' checkbox under 'Tweaks' if booting from native VHD by Windows.


    Is it possible to implement following configuration ?



    Thanks & Regards.....

  20. Hi 'JFX'.....


    Thanks for useful info...........

    I prefer Dual Boot of latest Windows OS (Win10TP) but I don't want to use two Partitions for two OSes. I want to keep all Installation files and folders of Both OS in a single partition. It's why I using 'WIMBoot + VHDX'. I am using 'VHDX' because it allow me to keep two OSes in a single partition. And If one OS is corrupted then I re-install it within form second OS and vice-versa. And there is no need to format two Partitions again and again. And It very comfortable for me to just delete a 'VHDX' file in order to remove a OS completely without formatting a whole partition. And Before deleting 'VHDX' file I can cut-paste my Imp. Data within fro 'VHDX' to the root of same Partition which contains 'VHDX'. And By this way I don't have backup my Imp. Data to any other Storage Device. And After re-installation of Windows within 'VHDX'. I reverse the cut-paste process.


    As I am using tetra boot of 'Mac OS X' , 'Win 10 TP' , 'Win X TP' and 'Ubuntu 14.10'. So I want to keep minimum number of partition in my Hard Disk.


    You mean 'VHDX' require/consume more size in order to hold WINDOWS? If 'Yes' , then what about 'VHD' or any other 'Virtual Disk Drive' ? Does 'VHD' also require more size ?


     I can not compromise with 'Hibernate' feature so what should I do so that I can keep two Windows OS in one partition along with WIMBoot ? Is there any solution ?


    I have only 3GB RAM. So Will it be safer to disable 'pagefile.sys' in my Case ? or not ?


    Please suggest me a trick/method by which I can keep two WIMBooted OS within same partition with 'Hibernate' features....


    Thanks & Regards....

  21. My Laptop is 'Dell Inspiron 1545' which is a MBR/BIOS type........

    I have recently installed WIN10TP as 'WIMBoot + VHDX' configuration in my system which is created with the help of 'WinNTSetup v3.7'.

    Everything is working just fine. But there is no option for 'Sleep'. Why ?

    Does 'Sleep' feature is not supported in WIMBoot ?

    Why I am unable to use 'Sleep/hibernate' features if I use 'WIMBoot + VHDX' configuration ?

    Is there any role of 'WinNTSetup' for not accessing 'Sleep/hibernate' feature ?

    I want to keep My Installation Drive as small as possible so I want to disable 'pagefile.sys'. Is there any serious drawback of disabling 'Pagefile.sys' ?


  • Create New...