Systems Deployment : Deploying Windows 10 LTSB Legacy: getting "An operating system wasn't found". VM is set to BIOS

Deploying Windows 10 LTSB Legacy: getting "An operating system wasn't found". VM is set to BIOS

I don't know what I'm doing wrong here. I'm filling in for the guy that left, but I don't really know much about any of this. In over my head.

The VM I created is definitely set to BIOS, and if I do a msinfo32 command, BIOS shows LEGACY.

Please help me. I will do my best to provide any info requested.

Thank you.

3 Comments [ + ] Show comments

Did you mess with the Boot file or BCD? The only time I ever get these errors is if they are missing from the primary partition or corrupt. Can you deploy this image to a physical device? - Keltonfoss 5 years ago
Not that I am aware of. I cannot successfully deploy to a physical device, I haven't tried a virtual, though I did create the image on a VM.

I don't actually know how to mess with the boot file or BCD. - TippsAttack 5 years ago
- Sounds like either something went wrong during sysprep - or your MBR is out of whack. If this is still an issue i can find you the articles to fix it - Keltonfoss 5 years ago
  - I'm in agreement with you on the MBR side. I really feel like that's the issue. I can't think of anything else. I've recaptured this thing so many times.
    
    I just bumped the size from 200 to 500 in hopes that it was just a size issue. - TippsAttack 5 years ago
@tipps Win10 does in fact need to be 500, I apologize that's something i should have thought of first and foremost, considering about a year ago i had to get on the phone with Kace to figure that one out! - Keltonfoss 5 years ago
- that turned out to be it! Interesting because a previous win 10 image works for the 200, but, meh, 500 is it for now on.
  
  Thank you for the help! - TippsAttack 5 years ago

Be the first to answer this question

Answer this question

Systems Deployment Questions

question