Windows 10: Start a program from a batch file

4 Apps of mine run a batch file that -tries- to call/start and EXE program. These Batch files need to work with OS XP thru Win 10. Win 10 has a pop-up window asking user if its okay to run/execute my EXE. No other Win version does this and thus I suspect a timing problem.

Here is a few lines from my BAT file:
Code: if %WinVer%-5.0 LSS 0.0 (pause) else (timeout /t 8) call %od-tools%\base4DOS.exe /openLF %FCname% %od-user% %FCexit% > nul @echo off[/quote] I have tried the following but will this work on older OS versions?
Code: start /wait "" "%od-tools%\base4DOS.exe" /openLF %FCname% %od-user% %FCexit% > nul[/quote] This doesn't work either. Any suggestions?

Thanks, Phil

:)

 

Start-up batch file

I have a batch file that runs upon start-up. It has worked FINE from Win3 onwards, modified as necessary for each version of Windows. However, now I've got WinX, it doesn't work as it used to.

Specifically, this line works just FINE:-

Start "C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXE" "C:\Data\My WORD Documents\My File.docx"

... but NONE of these commands below does what I want it to, i.e. to load Excel and open a file, then get on with the Batch File:-

1.

"C:\Data\Excel\My File.xlsm"

2.

Start "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office\Microsoft Excel 2010.exe" "C:\Data\Excel\My File.xlsm"

3.

Start "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Office\Microsoft Excel 2010.exe"

4,

Start "C:\Program Files (x86)\Microsoft Office\Office14\Excel.exe" "C:\Data\Excel\My File.xlsm"

5.

"C:\Program Files (x86)\Microsoft Office\Office14\Excel.exe"

No. 5 works, but a) it (obviously) doesn't load the file I want, and b) the Batch File then hangs.

Help !

 

Check disk on a 1 bad sector but drive is 88% healthy, sshd 2 b mbr

The results are as follows;

U:\>

U:\>Stage 1: Examining basic file system structure ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1048064 file records processed.

'1048064' is not recognized as an internal or external command,

operable program or batch file.

U:\>File verification completed.

'File' is not recognized as an internal or external command,

operable program or batch file.

U:\> 8622 large file records processed.

'8622' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 bad file records processed.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 2: Examining file name linkage ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 17170 reparse records processed.

'17170' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1155756 index entries processed.

'1155756' is not recognized as an internal or external command,

operable program or batch file.

U:\>Index verification completed.

'Index' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 unindexed files scanned.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\> 0 unindexed files recovered to lost and found.

'0' is not recognized as an internal or external command,

operable program or batch file.

U:\> 17170 reparse records processed.

'17170' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 3: Examining security descriptors ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\>Security descriptor verification completed.

'Security' is not recognized as an internal or external command,

operable program or batch file.

U:\> 53847 data files processed.

'53847' is not recognized as an internal or external command,

operable program or batch file.

U:\>CHKDSK is verifying Usn Journal...

Invalid parameter - verifying

U:\> 35872856 USN bytes processed.

'35872856' is not recognized as an internal or external command,

operable program or batch file.

U:\>Usn Journal verification completed.

'Usn' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 4: Looking for bad clusters in user file data ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1048048 files processed.

'1048048' is not recognized as an internal or external command,

operable program or batch file.

U:\>File data verification completed.

'File' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Stage 5: Looking for bad, free clusters ...

'Stage' is not recognized as an internal or external command,

operable program or batch file.

U:\> 297247241 free clusters processed.

'297247241' is not recognized as an internal or external command,

operable program or batch file.

U:\>Free space verification is complete.

'Free' is not recognized as an internal or external command,

operable program or batch file.

U:\>Adding 1 bad clusters to the Bad Clusters File.

'Adding' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>Windows has made corrections to the file system.

'Windows' is not recognized as an internal or external command,

operable program or batch file.

U:\>No further action is required.

'No' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>1950916280 KB total disk space.

'1950916280' is not recognized as an internal or external command,

operable program or batch file.

U:\> 760452004 KB in 448531 files.

'760452004' is not recognized as an internal or external command,

operable program or batch file.

U:\> 263136 KB in 53848 indexes.

'263136' is not recognized as an internal or external command,

operable program or batch file.

U:\> 4 KB in bad sectors.

'4' is not recognized as an internal or external command,

operable program or batch file.

U:\> 1212176 KB in use by the system.

'1212176' is not recognized as an internal or external command,

operable program or batch file.

U:\> 65536 KB occupied by the log file.

'65536' is not recognized as an internal or external command,

operable program or batch file.

U:\>1188988960 KB available on disk.

'1188988960' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\> 4096 bytes in each allocation unit.

'4096' is not recognized as an internal or external command,

operable program or batch file.

U:\> 487729070 total allocation units on disk.

'487729070' is not recognized as an internal or external command,

operable program or batch file.

U:\> 297247240 allocation units available on disk.

'297247240' is not recognized as an internal or external command,

operable program or batch file.

U:\>

U:\>C:\WINDOWS\system32>

 

Can you please post a screenshot of the popup message?

I'm guessing it might be a 'smartscreen' message as you don't specify it. I get this popping up sometimes when installing less common programs I've just downloaded. It's more widely described as an internet site filter.

But quite why that would be the popup you encounter in this case isn't obvious.

Assuming my guess is correct, the following should help you decide what to do. You scan also research 'smartscreen'.

 

Its titled 'User Account Control' and is a pop-up box that may be causing my problem.

I've done a lot of testing between my Win 7 and Win 10 laptop. Here is some code with comments ...
Code: rem 1. .bat works in All Win.s except Win 10!!rem call %od-tools%\base4DOS.bat /openLF %FCname% %od-user% %FCexit% > nul rem 2. .bat works in All Win.s except Win 10!! rem works! start /wait /B "%FCapp%'s DOSbox Setup" %od-tools%\base4DOS.bat /openLF %FCname% %od-user% %FCexit% > nul rem 3. .exe starts for a split second and then exits in Win 10... a Nogo! rem It has a 'User Account Control' pop-up box that may cause a timing problem. rem It works in Win 7. start /wait /B "%FCapp%'s DOSbox Setup" %od-tools%\base4DOS.exe /openLF %FCname% %od-user% %FCexit% > nul[/quote] EXE runs for a split second, then terminates ... ideas?

Phil

 

Hi, UAC was introduced in Vista, then its impact somewhat reduced. It's meant to give the user a last ditch option to block malicious programs.

You can turn it off altogether:




Otherwise the second answer here:
Add application to UAC exceptions

may point you in the right direction.

 

That helped ... I use Inno Setup to install my packages. Under [setup] 'PrivilegesRequired=admin' was changed to 'PrivilegesRequired=none' and that did the trick.

Their was another issue with the Start cmd. I was using 'start /wait /b' and that is a bug. 'start /b /wait' fixed problems.

Thanks for your help, Phil