blue iris windows service doesn't start upon reboot

[baikal]

Not sure this is since 5.2.4.4 as I haven't reboot it for quite a while maybe a few weeks, and I've set it to automatically download/install upgrade.

But it's recently as the upgrade is used to triggered in the night and by the morning I'll find blue iris has died. First the windows service shows running, so I restart the service or reboot computer will fix it. Began since yesterday or day before yesterday, I notice the service won't start automatically after reboot. At the time the version is 5.2.4.4, then this morning I run the desktop version it prompted upgrade so now it's on 5.2.4.5. Yet after reboot the service still won't start until I had to manually start it from the service panel.

Then I tried to remove windows service from startup option, reboot, then add it back in the startup option, no fix. The service still won't start by itself upon reboot.

The setup and everything has been working flawlessly for almost a year since I initially set it up, and I always have the upgrade download/install automatically turned on, now I've just check it off.

Just now I'm curious so I open the windows event viewer, found an "Application Error":

Faulting application name: BlueIris.exe, version: 5.2.4.4, time stamp: 0x5e87a6a9
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0xfbc
Faulting application start time: 0x01d60b6bf78daa70
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: bfe774b2-368c-41b8-a020-ff9446b83dc3
Faulting package full name:
Faulting package-relative application ID:

[hotbrass]

I just installed update 64 5.2.5.3 and I have read all the instructions and no matter what I do it still fails to start service. HELP!

What is the defined procedure for fixing this bug? Why would BI release a update that will not properly install itself???

Thanks everyone!

[GBillR]

Have you tried this:

Under the "Startup" tab on settings, uncheck the top block for "Run as a Windows service". Close BI. Verify the service has stopped in task manager. Reopen BI and recheck that option on again. you will need o reenter the password for the account running the BI service. Close BI and reboot. See if it works.

-Bill

[Bluescamera]

My machine won't even start after this update. Windows just spins it wheel on a black screen. Update did the same thing after installing. I had service running, I'm sure this had something to do with it. Arghhhh.

[hotbrass]

Your BI wont even start?

Mine will start but it says something like BI service failed to start.

[Bluescamera]

It finally started after a few reboots but now after unchecking and checking services box in BI it asks for a "service logon" password which I never remember setting and don 't know. I might have to revert to a system backup to an old version and turn off updates as this one isn't good.

[Matts1984]

Your BI wont even start?

Mine will start but it says something like BI service failed to start.

When adding credentials, are you using BI application credentials or system credentials? This is asking for windows service credentials.

[hotbrass]

Have you tried this:

Under the "Startup" tab on settings, uncheck the top block for "Run as a Windows service". Close BI. Verify the service has stopped in task manager. Reopen BI and recheck that option on again. you will need o reenter the password for the account running the BI service. Close BI and reboot. See if it works.

-Bill

Did that many, many times. Had to revert back to 5.2.0.0. All is well now. Will try again when the current batch of bugs gets fixed. Or not since there is not enough testing before throwing us bug laden updates.

And again, where is the well written set of instructions for installing the current updates that require action on the users end to repair all the bugs in the updates???

[hotbrass]

Your BI wont even start?

Mine will start but it says something like BI service failed to start.

When adding credentials, are you using BI application credentials or system credentials? This is asking for windows service credentials.

System/device credentials. It prompts for my credentials using the device name.

[reddawg]

But it's recently as the upgrade is used to triggered in the night and by the morning I'll find blue iris has died. First the windows service shows running, so I restart the service or reboot computer will fix it. Began since yesterday or day before yesterday, I notice the service won't start automatically after reboot. At the time the version is 5.2.4.4, then this morning I run the desktop version it prompted upgrade so now it's on 5.2.4.5. Yet after reboot the service still won't start until I had to manually start it from the service panel.

Then I tried to remove windows service from startup option, reboot, then add it back in the startup option, no fix. The service still won't start by itself upon reboot.

For the first problem, the BlueIris service not starting automatically, try changing the "BlueIris" service so it starts "Automatically (Delayed Start)". It is possible that the BlueIris service is trying to start too early in the boot process and thus fails to start. Open Services, find "BlueIris" and change it from Automatic to Automatic (Delayed Start). In addition, under the Recovery tab of the service, make sure "First Failure" and "Second Failure" are set to "Restart the service".

Just now I'm curious so I open the windows event viewer, found an "Application Error":

Faulting application name: BlueIris.exe, version: 5.2.4.4, time stamp: 0x5e87a6a9
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0xfbc
Faulting application start time: 0x01d60b6bf78daa70
Faulting application path: C:\Program Files\Blue Iris 5\BlueIris.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: bfe774b2-368c-41b8-a020-ff9446b83dc3
Faulting package full name:
Faulting package-relative application ID:

The crashing problem could be a corrupted system file (Faulting module path: C:\WINDOWS\System32\ucrtbase.dll). The ucrtbase.dll is a dynamic link library that is part of Windows 10, possible part of the .NET framework. Try opening an administrator elevated CMD prompt and do the following:

C:\> SFC /scannow
C:\> DISM /Online /Cleanup-Image /CheckHealth
C:\> DISM /Online /Cleanup-Image /ScanHealth
C:\> DISM /Online /Cleanup-Image /RestoreHealth

The SFC command should report either "Windows Resource Protection did not find any integrity violations" or "Windows Resource Protection found corrupt files and successfully repaired them". The DISM commands should report "No component store corruption detected". If no problems are found or the crashing problems persists, then you could try the following:

1) Make sure you have excluded C:\Program Files\Blue Iris 5 from your Antivirus as well as C:\BlueIris\db, C:\BlueIris\New, C:\BlueIris\Alerts and C:\BlueIris\Storage.

2) You can try rolling back your version of Blue Iris to an earlier version. You would need to be using the "Blue Iris Update Manager" from https://blueirissoftware.com/forum/view ... f=4&t=1034 or Blue Iris Update Helper from https://github.com/bp2008/biupdatehelper/releases.

You can manually roll back to a previous version if you saved the older Update.exe from previous versions. The Update.exe file is stored in either C:\ProgramData\Blue Iris\temp or C:\Program Files\Blue Iris 5.

3) It is possible that a Windows Update may have contributed to the crashing problem. You could try restoring Windows 10 to an earlier System restore point.