SCCM Capture media in Windows x64 not working – FIX

Fixing SCCM Capture Media That Won’t Autorun on Windows x64

If Configuration Manager capture media (the ISO used to capture a reference image) works fine when booted from a 32-bit version of Windows but doesn’t autorun the capture wizard when booted from an x64 image, the cause is usually that the AutoRun feature itself is disabled by default on the working directories/drive type involved on x64 builds, rather than anything wrong with the capture media itself. Rather than relying on autorun at all, the reliable fix is to browse to the capture media manually and launch the capture wizard executable directly from an Explorer window (or a command prompt) once you’re booted into the environment, bypassing the autorun mechanism entirely. If you’d rather have it launch automatically and are creating your own custom capture media, you can also address this at the source by explicitly enabling AutoRun behaviour for the relevant drive types via Group Policy or registry settings on the machine building/testing the media, though for a one-off capture, simply launching the executable manually is usually the faster fix.

Still Relevant on Current Configuration Manager (Updated for 2026)

The manual-launch workaround above still applies on Configuration Manager 2603, since AutoRun’s default-disabled behaviour on removable/optical media hasn’t changed on current Windows PE boot environments. Worth noting though: most current OSD workflows have moved away from standalone capture media entirely, capturing a reference image directly as part of a task sequence instead — if you’re building new deployment automation rather than doing a one-off capture, that’s the path worth setting up first, with this manual-launch fix kept as a fallback for whenever boot media is still the quickest option.