With the answer files complete, now it’s time to install Windows 10 on a reference Hyper-V virtual machine. You can naturally use any other virtualization platform for this, or even a spare physical PC, but I prefer Hyper-V and recommend it highly. To get started with Hyper-V in case you are not familiar with this
Search results for Customize Windows Image
Most new computers with pre-installed operating system today are shipped with a so called factory recovery option which allows user to completely reset the computer by restoring an image stored in specific factory recovery partition. The problem with factory recovery is that it restores everything as the original equipment manufacturer (OEM) wants. This might include a bunch of “bloatware”, useless software like “30-day trial of XYZ” or “Tweak your PC with this fabulous tweaker” and so on. One of the first things any user wants to do when setting up a pre-installed Windows on a new computer is to get rid of all this bloatware.
Final phase of this project is to sysprep customized Windows image, capture it to a WIM file, and create an ISO for completely automated installation. Create a Checkpoint On your reference Hyper-V VM, create a checkpoint before proceeding. Select Action > Checkpoint in Virtual Machine Connection window, name the checkpoint as you wish, click YES to
OK, now it’s time to create an answer file to automate Windows Welcome (OOBE). To do that, please launch the Windows SIM and create a new answer file (File > New Answer File). Because you already created the catalog file in a previous post in this series (Part 2) you don’t have to go through the
Installing Windows 10 is done in three phases: Boot from install media, run Windows Setup (when done, restart is required) Configure hardware devices (one restart during, one restart when done) Windows Welcome (OOBE) In normal clean install, user interaction is required in phases 1 and 3, phase 2 being run automatically without user interaction.
Boot & forget Of all the operating systems I know, Windows is the most versatile and flexible when it comes to setting up totally automated, unattended “hands free” install media. Pretty much everything you might want to do can indeed be done. It’s just a matter of knowing how! In this series of posts, we
My subjective opinion: Full Flash Update (FFU) imaging is the best thing that has happened to Windows deployment. Ever. Where capturing your deployment image to a WIM file takes 10 minutes, capturing it to FFU takes under two. The time required to apply an FFU image is cut to less than half of what it
With the holiday break over, it’s time to look back over our first year at Win10.guru before starting Year Two. A few years back, I was thinking about a website for advanced Windows users and IT professionals. Quite accidentally (it’s too long a story to tell here), I found myself the proud owner of a catchy
Especially when testing Windows Insider Preview builds in various editions and languages, I use differencing disks on Hyper-V virtual machines. This not only allows me to save storage space on my dedicated Hyper-V drive, but it also makes creating new virtual machines really fast, taking just seconds to boot to the desktop when a VM
Yesterday, I decided to do a clean install of the latest Windows Insider build 17711 on my HP ProBook laptop. I do traditional installs quite seldom, usually creating deployment images in Hyper-V. This is practical because Hyper-V standard checkpoints offer an easy way to restore a VM to any point throughout the process whenever something