FAQ
TL;DR: 260-character path limits apply—"In the Windows API, the maximum length for a path is MAX_PATH, which is 260 characters." Quote spaced paths, set Task Scheduler "Start in," or use a Startup .bat with START "" to close the console; Registry Run is a fallback. [Naming Files, Paths, and Namespaces]
Why it matters: This helps Windows 10 users auto-start Milesight VMS Lite reliably for uninterrupted recording.
Quick Facts
- Paths with spaces must be wrapped in double quotes in batch files, shortcuts, and Scheduler. [Elektroda, perzan, post #17114026]
- In Task Scheduler, set Start in to the app’s folder or Windows may default to System32 or the user profile. [Elektroda, perzan, post #17114026]
- To avoid a persistent console from a .bat, use: start "" "C:\Program Files (x86)\Milesight VMS Lite\Milesight VMS Lite.exe" then exit. [Elektroda, clubs, post #17114970]
- Placing the .bat file itself in Startup worked; a shortcut to it did not. [Elektroda, mlassota, post #17114663]
- Edge case: A .bat can be removed from Startup by security/OS actions; keep it minimal or adjust exclusions. [Elektroda, mlassota, post #17116465]
How do I auto-start Milesight VMS Lite reliably on Windows 10?
Use a simple batch file and place it in Startup. 1) Create a .bat containing the quoted EXE path. 2) Put the .bat itself (not a shortcut) into the Startup folder. 3) Restart and confirm VMS Lite opens. This method worked even when shortcuts and Scheduler failed. It may leave a console window; see the next answer to hide it. [Elektroda, mlassota, post #17114663]
How do I hide the console window when launching via a batch file?
Call the app with START and an empty title, then exit. Example: start "" "C:\Program Files (x86)\Milesight VMS Lite\Milesight VMS Lite.exe" followed by exit. Do not use /W if you want the console to close immediately. As one expert noted, "If you do not use start / w it will close the console after 'opening' the program." [Elektroda, clubs, post #17114970]
Why won’t my Task Scheduler task launch Milesight VMS Lite?
Incorrect quoting or a missing Start in directory commonly breaks tasks. Quote the full path to the EXE and set Start in to the application’s folder. Without Start in, Scheduler can try launching from System32 or your profile, and the app fails. As one expert put it, “quotation marks are the most common windows ill.” [Elektroda, perzan, post #17114026]
What’s the correct way to quote a path with spaces?
Wrap the entire path in double quotes. Example: "C:\Program Files (x86)\Milesight VMS Lite\Milesight VMS Lite.exe". Apply this in batch files, shortcuts, and Task Scheduler’s Action fields. “But above all, quotation marks are the most common windows ill.” Consistent quoting prevents mis-parsing and launch failures. [Elektroda, perzan, post #17114026]
What should I put in Task Scheduler’s Start in (optional) field?
Set it to the program’s installation folder. Example: C:\Program Files (x86)\Milesight VMS Lite. This ensures the process starts with the correct working directory. Otherwise, Windows can default to System32 or your user profile, causing file resolution issues at launch. [Elektroda, perzan, post #17114026]
START does nothing when I try it—what did I do wrong?
START treats the first quoted string as the window title. If you omit a title and your path is quoted, it may not launch. Provide an empty title before the path: start "" "C:\path\app.exe". This resolves the no-launch symptom with spaced paths. [Elektroda, perzan, post #17115325]
A shortcut in Startup doesn’t work—should I put the .bat itself?
Yes. In this case, placing the .bat file itself in Startup worked, while a shortcut did not. Using the direct .bat avoids resolution or permission quirks that sometimes affect .lnk processing at logon. [Elektroda, mlassota, post #17114663]
My .bat keeps disappearing from Startup—what should I check?
Check antivirus and security policies. One user observed the .bat being removed when using START, but not when calling the EXE directly. Add exclusions or simplify the script if it triggers cleanup. If removal persists, consider the Run registry method. [Elektroda, mlassota, post #17116465]
Can I run Milesight VMS Lite as a Windows service instead of at logon?
Only if the app is service-friendly. UI-bound apps often fail as services. As one expert cautioned, “on the condition that the program itself can be pressed into such a framework.” Test carefully, or prefer Startup/Run for GUI recorders. [Elektroda, Matuzalem, post #17114223]
Why does it start from the desktop but not at boot/logon?
Environment and working directory differ at boot/logon. Missing quotes or Start in can break launches outside your desktop session. Fix by quoting the path and setting Start in to the install folder, or use a minimal Startup .bat. [Elektroda, perzan, post #17114026]
How do I add Milesight VMS Lite via the registry Run key?
Use the Run key to trigger the app at user logon. Create an entry under the Run registry location that points to your EXE or .bat. This bypasses some Startup folder quirks and keeps autostart simple. [Elektroda, clubs, post #17116666]
Can long paths or special characters break autostart or tasks?
Yes. Windows legacy MAX_PATH is 260 characters, which can break launches. Keep paths short and simple. If you hit this limit, shorten folder names or relocate the app. This reduces argument parsing errors in tasks and scripts. [Naming Files, Paths, and Namespaces]
