Fix 0X000009D2 NERR_CantOpenImageFile Remoteboot Server

I know this error is infuriating—you're mid-deployment and the server just refuses to open the image. Let's get you back up and running.

The Immediate Fix

First, check the obvious: the image file path on the Remote Installation Services (RIS) or Windows Deployment Services (WDS) server. The error 0X000009D2 almost always means the server can't access the .sif or .wim file it's trying to load.

On the server, open Services.msc and confirm the Remote Installation or Windows Deployment Services service is running.
Right-click the service, choose Properties, and note the Log on as account. It's usually LocalSystem or a domain account.
Open a command prompt as Administrator and test the path directly. For RIS, type:
```
dir \\\REMINST\RemoteInstall\\I386\.sif
```
For WDS, it's usually:
```
dir D:\RemoteInstall\Images\\.wim
```
If you get an Access Denied or Path not found, that's your culprit. Go to the folder in Explorer, right-click, and hit Properties.
On the Security tab, make sure the service account (or Everyone, if you're in a pinch) has Read & Execute permissions. Add it if missing.

After fixing permissions, restart the service and try the deployment again. Nine times out of ten, that clears it.

Why This Works

The error code maps to a network share error—the server literally can't open the file over the network or even locally because the account it runs under lacks the right to read the image. I've seen this trip up admins who moved an image folder to a new drive and forgot to re-apply ACLs. The service account might be LocalSystem, which has broad local rights, but if the image lives on a different volume or a network share, it needs explicit permissions.

Less Common Variations

Sometimes it's not permissions. Here's what else I've run into:

1. Corrupted Image File

If the path and permissions check out, the image might be corrupted. Run chkdsk on the drive, or re-import the image in WDS. For RIS, re-copy the .sif from a known-good source. I once spent three hours on a permissions wild goose chase when the .sif was truncated from a bad network copy.

2. Network Share Pathing Issue

If you're using a custom share, verify the share exists. Open \\\REMINST in Explorer. If you can't see it, the share isn't there. Recreate it with net share REMINST=C:\RemoteInstall /grant:everyone,READ—but note that's a quick fix, not a secure one. Better to use the WDS console to reset the share.

3. DNS or NetBIOS Name Resolution

If the server is accessed by name and the client can't resolve it, you'll get this error at boot. Test with ping from the client. If it fails, check DNS or add an entry to the client's hosts file for testing.

4. Service Account Password Expired

If you're using a domain account for the service, its password might have expired. Head to Active Directory, reset the password, and update it in the service properties. The service won't start or will act flaky otherwise.

Prevention for Next Time

Set up a recurring alert for service account expiry—PowerShell can check msDS-UserPasswordExpiryTimeComputed. Also, document where your images live and who has access. After any server migration, test image access immediately with a simple dir command before you schedule a deployment. And if you're still on RIS, plan your move to WDS—Microsoft killed RIS years ago, and WDS handles permissions more gracefully.

Keep this error in mind; it's a classic. Fix the permissions, verify the path, and you'll be deploying images without the headache.