# Troubleshooting (PSImage)

<p class="callout danger">PSImage is not supported by FileWave Support. Do not open Support tickets for PSImage troubleshooting. This page is provided for educational use. If you want consulting assistance with PSImage setup or customization, contact <professional.services@filewave.com>. Existing unused Professional Services hours may be usable for this work. Feedback can also be sent to the same address. PSImage discussion happens through [Discord](https://kb.filewave.com/books/community-engagement/page/filewave-discord-server "FileWave Discord Server") or [Professional Services](https://kb.filewave.com/books/community-engagement/page/professional-services-training "Professional Services & Training"). For the official Windows Imaging solution, see [Network Imaging / IVS](https://kb.filewave.com/books/network-imaging-ivs "Network Imaging / IVS").</p>

**Q:** Error copying files from z:\\scripts when booting from physical PC. Works fine when booting from VM.

**A:** Windows PE either does not have the correct driver for the Ethernet NIC in this PC, or it has a driver that is not optimal. The network connection can be slow to come up and may be unavailable when imaging attempts to map the PSImage share. Inject the correct NIC driver into `boot.wim`, then update it on your USB thumb drives, WDS server, or Fileset. See [Tracking Imaging and Adding Drivers](https://kb.filewave.com/books/psimage-alternative-windows-imaging/page/tracking-imaging-and-adding-drivers-psimage "Tracking Imaging and Adding Drivers") for details.

**Q:** Sysprep fails with the following error in setuperr.log - "Audit mode cannot be turned on if reserved storage is in use. An update or servicing operation may be using reserved storage."

**A**: Open Windows Updates and install all pending OS updates to clear out the reserved storage and re-sysprep again. More info [here](https://techcommunity.microsoft.com/t5/storage-at-microsoft/windows-10-and-reserved-storage/ba-p/428327).

**Q:** Sysprep fails with the following error in setuperr.log - "Package &lt;PackageFullName&gt; was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image."

**A:** Run `remove_app.ps1` on the client PC from the Sysprep folder to remove the offending Microsoft Store app, then try Sysprep again. Keep checking `setuperr.log`. This can happen with multiple apps, but Sysprep stops at the first app it finds with this condition.

**Q:** Sysprep fails with the following message in `setuperr.log` - "Failure occurred while executing 'CAPISysPrep\_Generalize' from C:\\Windows\\system32\\capisp.dll."

**A:** Trigger sysprep locally from the reference system with the following command.

```bash
c:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:c:\Windows\System32\Sysprep\unattend.xml

```

**Q:** Dism fails with an error 2 when restoring a disk image to a PC that has a client mapping in image\_mappings.txt.

**A:** Verify that the disk image name mapped to that device serial number exists in the images folder. Edit the mapping entry so the assigned disk image name matches one of the captured disk images.

**Q:** Post-imaging hangs with repeated message "Waiting 10 seconds for initial inventory to complete" for longer than 5 minutes.

**A:** This is caused by the client being unable to communicate with the FileWave Server, such as when there is a device conflict. Check that **Automatically resolve conflicts** is enabled and set to **Replace old clients with new**.