Recording Service will not start with windows after upgrade to windows 10 from 7

[Reddwarf]

I just discovered that the recording service does not start here either after the win X upgrade. It is set to automatic start in Services.msc but it does not. In addition, lots of .net stuff was not enabled so NEWA would not start. On win7 prior to the upgrade everything was working normally.

[spab]

This also happened to me after upgrading to Windows 10, after checking the Event Viewer I discover that the service was timing out. I'm not sure why upgrading caused this to start happening but to fix it visit the following page to find out how to increase the timeout.
http://serverfault.com/questions/622432/...up-timeout

[donbrew]

I got a flash by error message about an NPVR Service needing to run elevated. It flashed too quick for me to make sense of it.

That is a fresh install of the newest NPVR on an upgrade 10. I only have the one Admin account on the machine, That doesn't elevate?

[Tinker]

Same thing is happening to me. Any ideas on this yet?

[sub]

Do you have an nrecord.log?

[Tinker]

Do you have an nrecord.log?

Here is my log.

[johnsonx42]

your nrecord service is starting just fine... what makes you think it isn't?

[sub]

Yeah, the logs look like it's starting fine.

[Tinker]

your nrecord service is starting just fine... what makes you think it isn't?

Why does the log say "Marking recording (5863) as 'Recording service not running at recording time'"? Every recording fails until I right click the icon in the tray and "restart recording service". After the restart everything works fine. If I reboot the PC this happens again and I need to restart the recording service again. Not sure why this happens. One small detail that probably is not significant. After a reboot the NTray icon has funny white dots around the icon like there are some pixels that should be transparent but are not. After restarting the recording service this goes away and the icon looks very clean.

It seems like this issue is very easy to reproduce because it happens after every reboot. Any ideas on resolving this would be great. Thanks!

[sub]

Post the logs again, and this time tell us the name / time of a recording that failed. We'll take a look what happened.