Showing results for 
Show  only  | Search instead for 
Did you mean: 

Creating a Windows 10 VM

No ratings



This document will guide you through the process of creating a Windows 10 VM. We assume that you have read the advice in McAfee Sandbox - Creating a VM Image regarding whether you actually need a Windows 10 VM and decide that you want to build one anyway. Due to the increased security built into Win10, customers encounter problems when building these VMs and hopefully this will explain why and what to look out for. Feedback - good or bad - is always welcome and it is intended that this document will be somewhat dynamic and updated according to feedback received.



To create the VM we will use VMware Workstation 12.1.png






 For Windows 10, choose Virtual Machine Version: 11


We are using build 1703 from the supported list in Install Guide5.png

Enter admin account and windows product key6.png








































Log into the windows VM and install VMWare tools

 Copy over your installation packages and install them on your VM







Open Task manager and disable everything from starting with windows, except VM tools, we will uninstall those later

 In control panel navigate to the user settings and disable UAC for administrator

 Once all the software is installed run the VMDK Provisioning tool





Once machine has rebooted, vmware tools is uninstalled, and by running the whoami command from CMD we see the local administrator account is now being used25.png



Because we now have a new windows profile, please go through and disable UAC for administrator

Open all the programs you installed and clear the wizards, including internet explorer, otherwise these wizards will launch each time the VM is run in ATD.

 When you are happy everything in the VM works OK, rerun the VM Provisioning tool one last time

 After the final reboot, open task manager and check that installingmsi is running.26.png



 This is installed by the provisioning tool and is essential to the VM creation process in ATD.

Shut down the VM and proceed to upload the VMDK file to ATD using an FTP tool such as Filezilla or WinSCP.

NOTE: Our Demo .vmdk file is named Windows10  x64 Demo. When the vmdk is imported into ATD, you have the opportunity to rename the img file to something else. In the Installation Guide, section Convert the VMDK and VHDX file to an image file , there are a couple of things to note here:

  • The Image Name must not contain a space or any special characters. ( hypens (-) or underscores (_). are allowed. )
  • Ensure that you specify whether the OS is a 32-bit or a 64-bit in the Image Name field, else the samples will fail submission.
  • McAfee ePO and OS profiling work only when you use the default name shown in the table in this section of the Install Guide. This is a restriction from the ePO side. If you intend to use this feature on ATD you MUST use the names in this table for your VM. If you do not use this feature the naming is not important.
Labels (1)

Pics not showing, please fix links.



now is ok

Version history
Revision #:
3 of 3
Last update:
‎01-24-2019 08:39 AM
Updated by:

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community