New
#600
If I enabled the "Suspend Updates" option and enabled the "Windows Insider Program" feature, would I only be able to download and install the latest testing build of Windows 10 or not?
Thanks
Bye
If I enabled the "Suspend Updates" option and enabled the "Windows Insider Program" feature, would I only be able to download and install the latest testing build of Windows 10 or not?
Thanks
Bye
Just curious,
Is anyone else experiencing an issue with SetupComplete.cmd running too early in version 1703?
No matter what I try, the batch file just seems to run too early, causing it not to run when it actually enters the Administrator profile for the first time. I know it has "tried" to run at some point during Windows setting itself up because I can see that some of the things I have put in the setupcomplete.cmd file have executed (downloads other scripts and stuff....). It is like the script starts to run prematurely, then the system must be rebooting itself causing it to stop the script. Then when it comes back up to login to the Administrator profile for the first time it never executes because it has already tried to execute it. I do the images for where I work (a school district), and have made many Windows 10 images and never seen this issue with any of the past versions of Windows 10. If anyone else is experiencing this with 1703 please let me know, and if you know a fix that would be great haha!
Dustin Olson
Hi Kari, first of all: thank you so much for your tutorial on Sysprep and everything else in this and other forums.
I knew about Sysprep some time ago and I instantly thought that this was what I needed.
I was sure that Sysprep could lead me to a final .iso, but I just completed the whole procedure and I'm having only an .img (.mrimg, in my case, because I used Macrium Reflect - btw, Siw2's WinPE is not available for download anymore).
So my question is: is it possible, with this procedure, to obtain an. iso file (identical to a genuine MSDN Windows, but with .wim/.esd modified during Audit)?
I'm telling you the next steps I should do, after I'll have this .iso: modifying it with WinReducer, a software to slim the .iso down. I choosed this procedure (first: Sysprep, then: WinReducer) instead of the opposite (first: WinReducer, then: Sysprep) because I'd like first to have an .iso with all my software pre-installed, then slim it down with WinReducer. This could not be interesting for you, I know, but I told you just for you to know.
Here's the point of my doubts:
- What does sysprep exactly create - an iso, esd, wim, img or what?
- And, during which step Windows will use what sysprep created?
- If I completely misunderstood everything, what should I do to obtain a final .iso with all softwares and tweakings I need?
And... last thing:
- When I finally boot to desktop, after haveing sysprepped, imaged and oobe'd (so when I am booting Windows for the first time as a New User), I find all the hidden files that I had before on Admin account (i.e.: 2 desktop.ini on Desktop, Folders in Documents, files in C:, etc...); I've never had these files before, on every clean installation (without sysprep) of Windows I made until this with sysprep. Why?
Thanks for your efforts and your help, if you can. Good work!
As I have explained several times in this thread, the reason I use Macrium as deployment method in tutorial is that I have tried to make the process as simple to private users as possible. The Macrium method is viable and fast method to capture image and deploy (restore) i9t to another machine.
However, if you want to use more advanced methods to create a standard ISO image from your customized Windows image, see this tutorial: Create Windows 10 ISO image from Existing Installation Windows 10 Installation Upgrade Tutorials . Part Three in it is what you are looking for.
Kari
Note
Please notice:
Every now and then I get messages from members asking me to help privately, either per private messages, email, Skype and whatnot. Some have found my email address or request assistance on YouTube and Twitter.
I cannot talk for other senior members on Ten Forums, how they react to these messages, but my policy is strict: I will in no case offer any kind of private assistance, nor will I reply those messages requesting it.
The reason is simple: you describing your issue privately to me, me assisting you to resolve it again completely privately, it does not help other members with similar issues. The whole idea of a site like Ten Forums is that issues are posted in general areas, visible to all members and visitors alike, they may be replied and answered by multiple members, and possible resolutions can be seen by your fellow geeks facing similar issues. That benefits not only you but your fellow geeks, too.
Short: Please do not VM, PM, email, tweet your issues to me. I will not reply.
Kari
Last edited by Kari; 01 Aug 2017 at 19:15. Reason: Typos
I posted a question a few weeks ago (4th post up from this) that was about the setupcomplete.cmd batch file running too early, but have recently found out that this is not the "real" issue. The real issue is actually the auto-logon count in the unattend.xml file is being ignored. I have the count set to "1", but it seems like Windows keeps logging back into the Administrator profile multiple times (so instead of logging in just one time and being done as I have specified, it logs in multiple times). Every reboot sends me back to the Administrator profile.... Is anyone experiencing this as an issue? I have tried searching around the web and haven't been able to locate a fix for this (or even others experiencing the same exact issue). Let me know if anyone is experiencing this or if there are any suggestions, thanks!
Dustin Olson
All Macrium images can be mounted just like a 2nd hard drive or VHD/VHDX, etc. If you use Macrium to image a machine you generalized during sysprep you can either create a MacriumPE USB from the rescue environment it asks you to create when it's first installed, or you can mount the Macrium backup image on another system and then use Wimlib/ImageX/GimageX to capture that mounted Macrium backup image as a .wim
If you do not want to go about mounting it and capturing it that way then simply use the option within Macrium itself to create a rescue environment and then make a bootable USB stick out of it. When you want to apply your sysprepped image, just boot into Macrium's PE environment and apply it to the drive.
I have image of a 50 GB win 10 partition (not including System Reserved) (it has 15 GB data, image file size is 9 GB), generalized. What will happen if I use that image on a 40 GB partition and 60 GB partition on other computers?
Is there way to add drivers during audit mode?