Windows: Opening image sequences from the cli

Describe the bug

The docs states you can open image sequences on Windows using:

C:\Program Files\xSTUDIO\bin\xstudio.exe C:\Users\JaneSmith\Media\exrs\exr_sequence.####.exr

it actually fails:

E:\Ynput>h:\programs\xstudio_1.0.0\bin\xstudio.exe H:\AYON\projects\AY_CG_demo\shots\sh010\publish\render\renderLightingMain_beauty\v001\cg_sh010_renderLightingMain_beauty_v001.####.exr
[2025-08-27 18:35:34.022] [xstudio] [info] XStudio logging started.
[2025-08-27 18:35:34.233] [xstudio] [info] API enabled on 127.0.0.1:45500, session name default0
[2025-08-27 18:35:34.239] [xstudio] [error] Failed to load media 'No frames specified.'

It doesn't work until the frame range is specified:

C:\Program Files\xSTUDIO\bin\xstudio.exe C:\Users\JaneSmith\Media\exrs\exr_sequence.####.exr=1001-1050

Also note that passing only the first frame resulted in an exception:

E:\...\programs\xstudio_1.0.0\bin\xstudio.exe H:\AYON\projects\AY_CG_demo\shots\sh010\publish\render\renderLightingMain_beauty\v001\cg_sh010_renderLightingMain_beauty_v001.1001.exr
[2025-08-27 18:37:31.075] [xstudio] [info] XStudio logging started.
[2025-08-27 18:37:31.289] [xstudio] [info] API enabled on 127.0.0.1:45500, session name default0
[2025-08-27 18:37:31.304] [xstudio] [warning] auto __cdecl xstudio::scanner::ScannerActor::{ctor}::<lambda_3>::()::<lambda_2>::operator ()(const class caf::error &) const error("Invalid url")
[2025-08-27 18:37:31.304] [xstudio] [warning] class std::vector<struct std::pair<class caf::uri,int>,class std::allocator<struct std::pair<class caf::uri,int> > > __cdecl xstudio::utility::MediaReference::uris(void) const Invalid uri file:H:\AYON\projects\AY_CG_demo\shots\sh010\publish\render\renderLightingMain_beauty\v001\cg_sh010_renderLightingMain_beauty_v001.{:00d}.exr

To Reproduce

1. Use any windows machine.
2. Locate an image sequence.
3. try all formats and see which works.

Expected behavior

• The generic /path/to/frame.####.exr should open the entire image sequence.
• /path/to/frame.####.exr=0010-0030 should only be necessary when you want to limit the frame range.

Desktop (please complete the following information):

• OS: Windows 11 - 26100.4946

Reproduce the documented Windows CLI invocation with an image sequence, then compare it with the explicit frame-range form and the single-frame form. Trace the CLI media-opening and image-sequence parsing entry points; done means a generic .####.exr path opens the full sequence, an explicit range limits it, and a single frame no longer produces the reported invalid-URI exception.