Windows 10: Making command line programmer accessible system wide

First of all apologies if this is posted in the incorrect place and/or has been previously answered.

I recently installed Windows 10 on my laptop after being a long time linux user, I'm curious to see how much it differs from Windows 7.

I regularly download ISOs/Files with their corresponding MD5/SHA1 hash for verification, after a quick search I found a command line tool from Microsoft (FCIV) which calculates MD5 and SHA which is exactly what I need.

In previous versions of Windows I would just dump the file in system32 which would make it available system wide, having never really used a 64Bit version of Windows can I just place the file in C:\windows\system32 or is there some preferred location?

:)

 

Closing down Windows 10

Hi Paddy, you have done nothing wrong - is is simply down to bad programming on the part of the programmer who wrote the application which is stopping Windows from shutting down.

I am a software developer and always make sure my apps contain a line or two of code to handle system shutdown - it is just laziness on the part of the programmer and you pay the price . . .

if (e.CloseReason == CloseReason.WindowsShutDown)

{

// Handle System Shutdown

}

 

No Recovery Options or Changeable favorites Droplist

my Windows recovery bluescreen no longer displays anything but The UEFI and Startup options. I cannot access system restore, but have a line-command for it. I can't access Startup repair or Command Prompt X. Do they have command-lines?

my Favorites droplist obscures when I try to change anything's order. it will not work until I use The settings option of the three dots in the far left of The Microsoft screen.

 

Putting the pgm in system32 would still work. I'm not sure that it would carry over after a Feature update (Win10.1511, Win10.1607) - it might.

Consider creating a folder under your user folder specifically for portable apps.
This is a per user method:
Add the new folder to the Path environment variable so Windows looks in that folder for executables.

Using portaApps as the new folder name and Dad as the user login

Code: PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Users\Dad\portaApps;[/quote] Add the new folder as the last entry on the path.

 

Thank you, that is exactly the information I needed.