![]() To the running Windows system the vhdx file from which its running is the "C" drive. ![]() The vhdx physical windows instances of course can only be run singly (unless from inside a HYPER-V machine). Sometimes testing on real hardware is needed - VM's are fine as well if you don't need to test using the real hardware of course - but a disadvantage is that the VM's need a separate license !!!! especially if you run them concurrently. The disadvantage of a dual boot is well worth it for the convenience and performance - with the vhdx system the Windows instances are separate so they do not interfere with each other. Ībsolutely IMO no point any more in even thinking about the Sandbox if you can use multiple Windows instances with vhdx files/ These are persistent too and perform infinitely better than any sandbox. There would be no point in activating a virtual machine if it was used just to run Sandbox.Hi thereĪs it's so easy to create "Real" instances of Windows now as vhdx files (which are activated via digital license too) - and can also run totally from external HDD's / SSD's I find if I want test beds I simply create a new vhdx instance and run that. ![]() ![]() Sandbox is basically a stripped down enterprise build and runs unactivated. I know this is an old post but the above is not actually true. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |