FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Filewave 11 Imaging

Filewave 11 Imaging 16 May 2016 19:43 #2297

  • Darin Loertscher
  • Darin Loertscher's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 5
  • Karma: 1
  • Thank you received: 0
Gets a lot farther imaging than 10 did because now works with UEFI and multiple partitions (including the restore partition from the manufacturer). But after deploying an image I am getting a Boot Manager error saying I need to boot off a repair disk. I do that and the Windows Repair disk fails to fix. I have tried this only on a Lenovo out of the box running Win 7, and also after an upgrade to Windows 10. Do I need to turn of security or some other setting in the BIOS?
Attachments:

Filewave 11 Imaging 17 May 2016 07:37 #2299

  • Marcin Wcislo
  • Marcin Wcislo's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 1
  • Thank you received: 0
Thanks for indicating the issue. Could you please confirm that you have prepared your machine with sysprep and chkdsk before creating master image? The instruction how to prepare your machine for creating master image can be found here (description is written for Windows 7 but process should be that same for other Windows releases).

Another thing to check BIOS/UEFI settings if your machines are set to UEFI with CSM (Compatibility Support Module) mode enabled, at the moment native UEFI is not yet supported.
Last Edit: by Marcin Wcislo.

Filewave 11 Imaging 01 Jun 2016 19:23 #2323

  • Darin Loertscher
  • Darin Loertscher's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 5
  • Karma: 1
  • Thank you received: 0
I was having the exact same issue, and like the Filewave tech replied, you need to run chkdsk /R and also run sysprep...NOTE: run sysprep as an administrator by right clicking on sysprep and run as admin...this was key for it to work for me. Also, if sysprep fails, saying it can't validate your windows installation, then try out parts of this guide theitbros.com/sysprep-windows-10-machine-guide/ to uninstall some of the default installed Microsoft store apps that make it fail, then run sysprep as admin. The key app to uninstall is the WindowsStore itself, as it is what makes sysprep hang if there is no user logged in for it to authenticate against.
Last Edit: by Darin Loertscher.
  • Page:
  • 1