6.0.3.6 New Logfile Entries

[jaydeel]

I've noticed these new entries in my Blue Iris logfile after updating.

I was sure I had done the exclusion, but the Level 1 message was accurate. Nice!

 

[Tinman]

still getting the error even after updating to 6.0.3.7. Ken said I needed a "Valid" process exemption. New to me, always have had it in there.

 

[Techie007L]

@Tinman Delete your two File exemptions (the top two entries) from there, and create a new Process exemption for BlueIris.exe. Exempting the BlueIris.exe file itself from scanning is not the same thing as exempting the actions of the BlueIris.exe process from scanning. Also, your file exemption is redundant because you already have the whole program folder exempted.

 

[Tinman]

@Tinman Delete your two File exemptions (the top two entries) from there, and create a new Process exemption for BlueIris.exe. Exempting the BlueIris.exe file itself from scanning is not the same thing as exempting the actions of the BlueIris.exe process from scanning. Also, your file exemption is redundant because you already have the whole program folder exempted.

well thanks, never knew there was a process exclusion. So I changed it but error still is popping up.

 

[Tinman]

I also just added blueirisadmin.exe....still no luck.

 

[Tinman]

I'm wondering if its due to my not default location. The installer gave me the option to specify location when I installed BI6, so wouldn't think that would be a issue.

 

[Techie007L]

You could try to rule that out quickly by creating a new folder in Program Files named "Blue Iris", copying the "BlueIris.exe" file over to it, and creating a process exception for the copied file. If the message stops appearing on Blue Iris startup, that would confirm it's looking for a hardcoded exception path.

 

[Tinman]

No luck with that as well, I'll send Ken another email. Thanks for the help !

 

[IAmATeaf]

Try with just the exe name and not the full path, code could be simply comparing against Blueiris.exe ?

 

[IAmATeaf]

Wonder why he added these checks to the running code rather than when doing a new install or installing updates.

To me that would be a more logical place rather than periodic checks in the running code?

 

[Tinman]

Try with just the exe name and not the full path, code could be simply comparing against Blueiris.exe ?

My BI demo i use for testing worked perfect first time I added Blueiris.exe as a process exclusion. I am still having issue with my main install, I have just about tried everything and reboots as well, still get error. I will keep digging.

BTW, my demo location is same as main machine, so that is not the issue. Stumped for now.

 

[Tinman]

Update: Finally got it fixed. I had entered so many things, I just removed the whole exclusion list and started over. It worked!
Some notes:

You must enter Blueiris.exe as a process rule (yes we had used file rules for years, but not anymore)
Ken said it also wouldn't hurt to add blueirisadmin.exe as well.

Off to test 6.0.3.8

 

[jaydeel]

You must enter Blueiris.exe as a process rule (yes we had used file rules for years, but not anymore)

I missed this too. I just checked my archive of old Help PDFs. The guidance has been there since 5.3.9.0 (1/31/2021)

 

[CrazyAsYou]

Update: Finally got it fixed. I had entered so many things, I just removed the whole exclusion list and started over. It worked!
Some notes:

You must enter Blueiris.exe as a process rule (yes we had used file rules for years, but not anymore)
Ken said it also wouldn't hurt to add blueirisadmin.exe as well.

Off to test 6.0.3.8

View attachment 239128

So just to confirm, although you/we add the parent install folder "C:\Program Files\Blue Iris" we also need to add the actual executable/process as well "C:\Program Files\Blue Iris\BlueIris.exe" ? - This seems odd to me, is it a bug in how Windows defender applies exclusions?

 

[IAmATeaf]

M

So just to confirm, although you/we add the parent install folder "C:\Program Files\Blue Iris" we also need to add the actual executable/process as well "C:\Program Files\Blue Iris\BlueIris.exe" ? - This seems odd to me, is it a bug in how Windows defender applies exclusions?

More likely a bug in the logic being applied in the code?

 

[jaydeel]

So just to confirm, although you/we add the parent install folder "C:\Program Files\Blue Iris" we also need to add the actual executable/process as well "C:\Program Files\Blue Iris\BlueIris.exe" ? - This seems odd to me, is it a bug in how Windows defender applies exclusions?

This my understanding...

If you exclude only:
C:\Program Files\Blue Iris\BlueIris.exe
or folder
C:\Program Files\Blue Iris\

Defender still scans:

• Every file BI writes
• Every file BI reads
• Every temp file
• Every stream buffer

If you exclude the process:
BlueIris.exe (Process)

Defender bypasses scanning for ALL file operations initiated by that process.

By excluding the process, it might seem redundant to also exclude:

• The root folder(s) for Blue Iris www, log, etc. subfolders (typically C:\BlueIris). These are specified in the Settings > Webserver, and the Status > Log tabs.
• All root folders in the Blue Iris Settings > Storage tab
• The Blue Iris Temp folder in Settings > Options... The default is 'C:\ProgramData\Blue Iris\Temp'. (I exclude the root folder 'C:\ProgramData\Blue Iris\'),

But doing so also covers the access of the files in these folders by other processes (like my various PowerShell scripts).

 

[Bruce_H]

I have been trying to get this warning message to go away with no success, I am running Bitdefender as my AV software

Here is what I have excluded from every type of scanning etc that I can in Bitdefender, and the warning still shows in my log files, is there anything that I am missing?

My www location is the default C:\Program Files\Blue Iris\www, I am not using any other location for BI than what I have listed (to the best of my knowledege)

c:\blueiris
c:\program files\blue iris
c:\programdata\blue iris
g:\blueiris
c:\program files\blue iris\blueiris.exe
c:\program files\blue iris\blueirisadmin.exe
c:\program files\blue iris\blueiristoaster.exe

 

[Tinman]

Not

I have been trying to get this warning message to go away with no success, I am running Bitdefender as my AV software

Here is what I have excluded from every type of scanning etc that I can in Bitdefender, and the warning still shows in my log files, is there anything that I am missing?

My www location is the default C:\Program Files\Blue Iris\www, I am not using any other location for BI than what I have listed (to the best of my knowledege)

c:\blueiris
c:\program files\blue iris
c:\programdata\blue iris
g:\blueiris
c:\program files\blue iris\blueiris.exe
c:\program files\blue iris\blueirisadmin.exe
c:\program files\blue iris\blueiristoaster.exe

I'm not familiar with Bitdefender, but does it give you the option of file-folder-file type-process? That is where I screwed up, I didn't have the right type.

 

[jaydeel]

I have been trying to get this warning message to go away with no success, I am running Bitdefender as my AV software

Here is what I have excluded from every type of scanning etc that I can in Bitdefender, and the warning still shows in my log files, is there anything that I am missing?

My www location is the default C:\Program Files\Blue Iris\www, I am not using any other location for BI than what I have listed (to the best of my knowledege)

c:\blueiris
c:\program files\blue iris
c:\programdata\blue iris
g:\blueiris
c:\program files\blue iris\blueiris.exe
c:\program files\blue iris\blueirisadmin.exe
c:\program files\blue iris\blueiristoaster.exe

Can you screenshot the logfile warnings you are seeing (see post #1)? Are they specifying Windows Defender? Are you seeing a level 0 message recognizing Bitdefender? If not, then that may be the issue.

 

[Bruce_H]

Here is the screen shot from my log file

Windows defender is not involved as I am using Bitdefender as shown in the log file