Forum Discussion
System environment variable Patch and registry
Ok, here's details:
here's file location C:\Windows\test\toy.exe
this my registry key
HKEY_CLASSES_ROOT\DesktopBackground\Shell\toy\command @="toy"
this is system variable Path: C:\Windows\test;C:\Windows\system32;C:\Windows;..... and so on
when I open command prompt (let say on desktop location) type: toy and enter, it works, so the path C:\Windows\test works, but the same command from registry doesn't. So, in this case path C:\Windows\test doesn't work and it drives me crazy. I don't understand at all how this is possible.
In this case what you could do is:
1- You verify the integrity of the application files, from your main repository folder. Not the HKEY_LOCAL
...at this point I am not sure of what the current problem exactly however, you can run a debug on your application to check files integrity.
x- You can use a checksum validation to verify whether the application function and logic follow the proper path in order to reach the consensus.
xx- If nothing is found, you should try a different checksum parity bytes or check in the
https://learn.microsoft.com/en-us/windows-server/storage/refs/integrity-streams
If you cannot see any validation files or a difference, since I suppose you have more than 1 folder containing the same file?
I would check the latest update on my server-pc-computer, I am thinking that if you did an installation from a different architecture type, then, it's possible that the controlling route now use an improved version and the initial function to start the app, or files have either move , or changed, or even be damaged...
If this app use a special package or limited files, and one files has been changed for X reason,
If the file is exactly the same, you could just change your diectory location to address the application when you call it.
Let me know if you find the issue!
Best regards!