Numerous examples of Windows 10 are available.
Numerous examples of Windows 10 are available.
Hi everyone, I work in a compliance testing lab. Clients often send products with instructions to install a specific software and risk damaging other settings. This situation has improved until recently when one installation caused my LabVIEW to freeze and halted three other clients' programs. I’ve considered two solutions and would appreciate your feedback or suggestions.
First idea: USB drives that start individual Windows 10 instances, wiping and reinstalling only after the project ends. Or save them for future repeat work.
Drawback: I suspect activation problems and potential legal concerns (uncertain in this region).
Second idea: virtual machines running Windows 10 with separate instances for each project.
Drawback: Legal versions may expire quickly, possibly straining system resources. I have limited resources—8GB RAM, a 3rd-gen i5 at 2.9GHz.
Any advice on which approach to explore further? Or is there another method I should know about? Some projects might work with Linux live boot, but most rely on Windows-only custom software. Thanks for your time!
I’d likely rely on several HDDs, and after testing, destroy each with a fresh Windows update.
Not always. Install once, turn it on, duplicate the HDD to several more drives. Microsoft probably won’t detect it. You’d have to invest more in additional hard drives. I’d consider installing on a virtual machine and then copying or cloning the virtual disk. Keeping multiple copies might cause all of them to share the same device ID. This limits you to using one at a time, swapping files as needed. Microsoft’s activation servers wouldn’t notice having 100 identical copies. This approach could be worth exploring. You’d have the ability to store all virtual disks on a big drive, organizing them by customer ID, project date, or whatever fits your workflow.
Running everything in a virtualized environment with Linux would use significantly less system resources compared to Windows. This lets you allocate more power to the virtual machine. It also removes the need for a Windows license on the physical hardware, making it easier to move licenses to the virtual setup. The only downside is dealing with Windows updates—if you have to apply them whenever you pull up an older disk file, it could waste a lot of time and you’d need to avoid data caps.