Windows 10 Creators Update: Startup and Services issues

Hi there, running build 15063.11 as of yesterday, and noticed that a few of my Startup shortcuts did not run successfully from C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup nor via Services (using nssm tool).

I made sure every shortcut and underlying app is configured to be run as Admin, more-so, I played around with the Services authorization (using local admin vs System, etc), all to no avail.

The only change was my upgrade to Creators Update yesterday.

 

Question Info


Last updated April 24, 2020 Views 1,875 Applies to:
Upon further investigation, it seems that the startup applications/services that are having issues are ones that try to grab a port (e.g. 3579) and are getting denied access (even though, as mentioned above, configured for Admin).

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I think you need to move this to the Insider section. 1703 isn't a public release yet.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

My bad - just moved it.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

For us to better understand your concern, kindly answer the following:

  • How did you setup your startup applications/services before? Did you use the NSSM tool to setup your startup applications/services?
  • What are the applications that you setup as a startup application?
  • Is the same scenario also happens when setting up your startup applications without using the NSSM tool?
  • Have you tried removing the startup applications that are having trouble opening, and then adding those applications again?
  • Can you still access the startup applications that are having trouble opening?

Hope to hear from you soon.

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi Argel,

  • One application was via a shortcut to the .exe into the aforementioned Startup path, and the other via NSSM.
  • Radarr via shortcut and Ombi via NSSM
  • The Ombi app won't load via NSSM (either manually nor at startup) after the Creators Update
  • I have tried removing and re-adding the applications/services
  • Both applications start-up normally manually

Thinking this might have something to do with the applications/services not being able to grab the appropriate ports, I ran the following to try:

netsh http add urlacl url=http://+:3579/ user=EVERYONE

Unfortunately that did not help.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I'm running into this same issue. Three apps that want to grab ports are being denied access to do so when starting as a service. If I run the apps from an admin-elevated command line they start fine. All three apps are starting as the SYSTEM account.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

FWIW, I used the following workaround and just created a VBS file to stick into my Startup folder (C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup):

https://superuser.com/a/198530

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have fixed the problem with my nssm based services. Just run the following from an administrative command prompt:

nssm set <servicename> appnoconsole 1

So in the case of Ombi it would be 'nssm set obmi appnoconsole 1' assuming you have called your Ombi service ombi

12 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you Vince, that indeed did the trick!

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.