Hello Wen Li,
Thank you for reaching out and for sharing such clear details about your system. Listing the files you checked and your exact build made this much easier to look into.
What’s happening
Nothing is wrong with your system. diskshadow.exe is part of the Windows Server tooling and is not included in Windows 10 client editions, including IoT Enterprise (build 19045). The files you found (vssapi.dll, vssvc.exe, swprv.dll) are the Volume Shadow Copy Service itself, which is present on your system as expected. Only the scripting front-end is absent, so this is not a sign of corruption, and sfc /scannow won’t restore a file that was never part of the image.
What you can use instead
- Confirm VSS is healthy: run
vssadmin list providersandvssadmin list shadowsfrom an elevated Command Prompt. - Create a snapshot with PowerShell:
(Get-WmiObject -List Win32_ShadowCopy).Create("C:\", "ClientAccessible") - Use
vshadow.exefrom the Windows SDK if you need scripted snapshots or want to expose a shadow copy. - Use Windows Server if
diskshadowitself is a hard requirement, since it’s included there by default.
If you let me know what you’re trying to accomplish (backup, mounting a snapshot, or exposing a drive letter), I’ll gladly suggest the best approach for your setup.
If this answers your question, please consider marking it as accepted so others with the same issue can find it easily.
Kind regards, Ntiganzwa Microsoft Support Community Contributor