Windows 10: Program running as Service cannot access NAS while logged in as User

I have a program that I would like to run as a service. The program requires access to read/write to my NAS. I have changed the service to Log On as my specific user account, in which the username and password match that of the shared NAS drive. This worked up until the recent Windows update. I believe there is an issue with the service editor username/password. When I run the program manually not within the service window then it can access the NAS without issue while I'm logged in as the specific user. But if I run the program using the Services either automatically on startup, or manually starting it then it cannot access the NAS.

:)

 

Running programs from NAS

I wonder if the programs that won't run from the NAS would run when installed on an External USB drive attached to the computer? In the past I've seen some programs that wouldn't run except when installed on a drive physically attached to the motherboard in the computer. I just tried a couple of rather simple programs, one said there was not enough space [58MB] available on a 1TB NAS HDD with over 400GB free and the other needed 9.6MB but didn't list any USB or NAS drives as possible destinations.

 

Running programs from NAS


Sounds like it might be an account permissions setting on your NAS. The upgrade to Windows 10 will generate new internal IDs for the accounts, even though they are the same user name and password. I've got no problems with my DLink NAS - but the only programs I run from it are setup/install programs. I also have no access errors when my media computer is playing videos from the NAS and I am reading/writing files to it on my laptop.

I do run a multi-game disk saved on my NAS called American Horrors - I had to map a drive letter for that. That would be about as close to actually running programs from the NAS - it has a main install program that runs directly off the NAS (via the mapped drive letter) then displays a menu of the available sub-programs for installation. It wouldn't wok without a mapped drive letter.

 

(Win10 Home) Log On Settings for Services reverting from User/Admin to Local System

Thank you for the prompt reply.

As part of the set-up, I have uninstalled the application. For the application installer, within the Compatibility tab I see under "Run this program in compatibility mode for:"

(only one option within the drop down list)

"Previous version of Windows".

After selecting the above and installing the application, I proceeded to set the "Log On As" from "Local System account" to "This account: .\User"

This was done after

Stopping both application services

Thereafter restarting both services

Log On As ".\User" remains

Upon accessing the application, the application becomes unresponsive.

Running the application again, the "Log On As" returns to Local System.

I have repeated the prior steps, while changing the application properties "Startup type: Automatic, Automatic (Delayed Start), Manual, Disabled"

Each results in the same issue.

Within the application and the installer for the application, under the "Compatibility" tab, I have run the compatibility troubleshooter and "Test the program..."

There don't appear to be any errors.

It seems that users running Windows 10 Pro aren't facing these issues and changes to the two application services Log On As ".\User" remain after restarting Windows and starting the application.



Also, while possibly unrelated, I selected a different application installer, and within the Compatibility tab many more options are available in the drop down list for "Run this program in compatibility mode for:"

Windows 8

Windows 7

Windows Vista

etc...

While, as noted with the application installer for Hysolid, the options in the drop down list for "Run this program in compatibility mode for:"

Shows only

"Previous version of Windows"

This is peculiar, as Hysolid is compatible with Windows 7 to Windows 10.