Can I run msg.exe on Windows 10 Home?

msg.exe is not installed in Home, but it is in Pro (and above). Having both, I've copied Win10 Pro's msg.exe to a usb and tried to run from the usb in Win10 Home. Just typing msg with no parameters should have given the 'help' text, but instead I got....

{Message(): LoadString failed, Error 15105, (0x00003B01)}

On the Pro machine there was also a msg.exe.mui in C:\Windows\System32\en-US. Copying that to an en-US folder on the usb let me at least run msg.exe to get the help text. I haven't tested beyond the (not very useful) function of sending a message to myself, but you won't get any further without a .mui file, it appears.

An MUI file is an integral part of any app and it won't run without its associated .mui.

The MUI resource technology, exposed in Windows Vista and later, has the following characteristics:

• Language-specific resource files are stored separately from the application code binary, so that a code change does not affect the resources.
• The resources for multiple languages can be deployed in a single installation or separate installations for each language.
• A resource is loaded and displayed according to the language of the application as set by the user.

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

I've not used msg much before, and in my tests have only been able to send a message to myself on the same machine. However, there are some tips here...

The msg command is intended to be used as a messaging system to terminal server users, not necessarily between two Windows 7 computers, for example.
In fact, I've had a very difficult time getting the msg command to work between two standard Windows machines like the net send command did. I usually get an "Error 5 getting session names" or an "Error 1825 getting session names" error.
However, some have had luck using the msg command in this way....

https://www.lifewire.com/msg-command-2618093

...and gives a registry fix that may help....

....or perhaps not - I still can's send a message from my 10 Pro PC to my Home one. Seems even on a company network with domain/terminal servers it's tricky to use, you may get some hints here...

https://social.technet.microsoft.com...w7itprogeneral