Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

  • Days Won


Atari800XL last won the day on December 28 2014

Atari800XL had the most liked content!

Community Reputation

11 Good

About Atari800XL

Profile Information

  • OS
    none specified
  • Country
  1. WinNTSetup v3.8.8.3

    Abbodi1406, nice to see you around... Let's not get into the image.exe timings anymore. I think the point is clear: Imagex.exe was almost "forgotten", but as Abbodi1406 found out, it can be useful for direct apply of UUP files, and fast as well, for some people (with old hardware/ disks?) even faster than the mighty WinNTSetup. If people are concerned with/ interested in this time difference, I'm sure they will try it themselves. That's it.
  2. WinNTSetup v3.8.8.3

    Sorry, forgot about that. Log file says "Operation took: 7:47 min)".
  3. WinNTSetup v3.8.8.3

    Last message about the difference between WinNTSetup apply and "manual" Imagex,exe 10.0.16299.15 (using unmodified/ unconverted UUP files). I have repeated all the tests, using PE versions from Windows 7 (3.1) upward. Tests were done on a spare laptop (Pentium dual core TT2370, 3gb, apply from external 2.0 usb hd to internal hd). Reboot between tests (no disk cache effect). For WinNTSetup (, the timer is stopped as soon as the apply stage is done (when it starts applying tweaks). Pretty much all tests show WinNTSetup takes 7:00 minutes, manual apply with Imagex.exe takes 4:55 to 5:00 minutes. I'm not coplaining about WinNTSetup at all (will still use it), I just wonder where this time difference is coming from. And of course, I wonder why Microsoft is "hiding" this fast UUP-functionality in Imagex.exe ...
  4. WinNTSetup v3.8.8.3

    OK, thanks, I was wondering about verify and temp folder. Yes, I measured by old-fashioned manual timer :-) But I don't want to go too much off-topic, just wanted to share the remarkable difference.
  5. WinNTSetup v3.8.8.3

    Repeated the test, with a reset inbetween. Still 5 minutes for imagex, 7 minutes for WinNTSetup. Does it have something to do where you set the temp/ extract folder, or maybe verify on/off? (Just blurting out something, as I said, the first time I tried imagex I thought maybe it skipped files, but it doesn't seem to be that way).
  6. WinNTSetup v3.8.8.3

    I'm still testing as well, my first test was with imagex.exe from the dism folder (using your GetWAIKTools) in PE. This was version 16299, x86, and gave no errors. But it looked to finish too quickly, so I thought something must have gone wrong. I cleared the partition again (didn't run the install), then ran WinNTSetup, to time how long that took. WinNTSetup did the apply in around 7 minutes. After that I checked the size of C:, around 5.6gb was applied. So I tested imagex.exe again, it finished in 5 minutes, also with 5.6gb applied. Huh? How can it be so much faster?! The install seems to have gone OK while I'm typing this, so lots of interesting stuff to test and analyze...
  7. WinNTSetup v3.8.8.3

    Did you know that the latest imagex.exe does support multiple "ref" parameters? (I sure didn't). It also supports "*.*": imagex /apply Education_en-us.esd 3 Z: /ref *.esd /ref *.cab imagex /apply Education_en-us.esd 3 Z: /ref *.* Abbodi1406 found out: https://forums.mydigitallife.net/threads/windows-10-imaging-customization-and-deployment.59187/page-28#post-1388789
  8. WinNTSetup v3.8.8.3

    Thanks. Just to be clear: when you manually apply with DISM (instead of WinNTSetup using Wimgapi), cab-to-esd is also necessary, isn't it? BTW, just finished the test, using the new 17035 UUP files, everything working OK! (Not that the new 17035 preview is all that interesting, but that's a different story...)
  9. WinNTSetup v3.8.8.3

    Sounds good, JFX! Will test ASAP... How did you get this working without converting the cabs? Are you converting "on the fly" in some way?
  10. WinNTSetup v3.8.8.3

    (in a Burns voice): "Excellent!!!" Thanks JFX, just tested and this works for me. I'm sure others might find this too radical (maybe we'll find another way to disable the Edge page displaying), but to me, this will surely do for now! Of course, we can always enable Edge again after setup (during "PostInstall"). Normally, I would run setup on offline systems, but for Pro versions with a Digital License, it's better to have Internet access during setup, I have found this will get the system activated faster. Thanks again for your great support!
  11. WinNTSetup v3.8.8.3

    If anybody knows a reg setting to get rid of the new (unwanted) Microsoft Edge page popping up after a clean install of 16299 (when online), I would really like to know it. I like my setups to be completely silent, Microsoft seems to come up with new stuff all the time. I have been looking with regshot, etc. but can't find anything... The only thing I can offer in return is this, to get rid of the stupid "people" icon in the tray: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\People] "Peopleband"=dword:00000000
  12. WinNTSetup v3.8.8.3

    ADK: https://download.microsoft.com/download/3/1/E/31EC1AAF-3501-4BB4-B61C-8BD8A07B4E8A/16299.15.170928-1534.rs3_release_amd64fre_ADK.iso
  13. WinNTSetup v3.8.8.3

    With Windows 10 Version 1709 Fall Creators Update, build 16299.15 now being RTM, are you planning on making WinNTSetup 3.8.8 "RTM" now, as well? Or does the MS release have nothing to do with your release schedule :-) Either way is fine by me, the beta3 is working just great in my (UUP) tests [thanks again for the UUP support], ESD was released today (they even call it RTM, after saying they wouldn't use that term anymore). (Insider) ISOs and ADK will probably be available next week.
  14. WinNTSetup v3.8.8.3

    Some might find the tweak useful, it suppresses the "new network found" on clean setup: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\NewNetworkWindowOff] Note that this is just an empty key, there are no values "inside" it.
  15. WinNTSetup v3.8.8.3

    Thanks for "hanging in there" with me, JFX, it gave me the push to investigate further. Now I have to admit it turned out to be my own fault after all. I apologize for bothering you, it turned out one of the reg tweaks was -not- the same as the ones I successfully tested before (you can guess what the problem was, I'm sure, but I'm too ashamed to admit). Once again sorry for this, and thanks again for helping to narrow it down. Result for now is: WinNTSetup fully supports UUP, so one of these days the "rtm" will become available on the Microsoft updates servers, downloading the files is super easy with MKuba's UUP dump, so anyone can download this "shiny" (turd) OS as soon as it is released to Insiders, and apply it in a heartbeat with WinNTSetup! No need for converting to wim or iso (at least not for testing, same goes for upcoming rs4 previews, of course). Cool stuff...