Windows 10: Double-click to run .bat - Windows cannot find file

[/quote]

Below are the results of these commands:
Code: C:\Windows\system32>sc config TRkWks start= auto[SC] ChangeServiceConfig SUCCESS C:\Windows\system32>net start TrkWks The requested service has already been started. More help is available by typing NET HELPMSG 2182. C:\Windows\system32>fsutil usn deletejournal /d /n c: C:\Windows\system32>chkdsk /scan The type of the file system is NTFS. Volume label is Win 10. Stage 1: Examining basic file system structure ... 425984 file records processed. File verification completed. 10186 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 558648 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. Stage 3: Examining security descriptors ... Security descriptor verification completed. 66333 data files processed. CHKDSK is verifying Usn Journal... 5024 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 249478143 KB total disk space. 108035960 KB in 296481 files. 187504 KB in 66334 indexes. 0 KB in bad sectors. 502603 KB in use by the system. 65536 KB occupied by the log file. 140752076 KB available on disk. 4096 bytes in each allocation unit. 62369535 total allocation units on disk. 35188019 allocation units available on disk.[/quote] Code: >where cmd C:\Windows\System32\cmd.exe >echo %systemroot% C:\Windows[/quote]
The problem persists.

 

The Creators updated installed moments ago.
bat and cmd files are now working properly again.

 

Reasonable outcome. Should this happen again, and you can't use a restore point, an in-place upgrade repair install should achieve the same. With the CU around now, a 1607 in-place upgrade repair install of a 1607 installation isn't necessarily the first choice.

 

No no no ... back it out so we can work on this some more!!! JUST KIDDING
Sure wish we knew what was wrong. Oh well, as long as it's working for you now.

 

My thoughts exactly! I was tempted to roll it back just so I could figure out what was wrong.