#Blue iris support Pc#
The video recording process on the Blue Iris PC likely just accelerate the McAfee memory leak. The problem is easily resolved with reboot. However on these PCs It take about 3 days to run up the memory to the point where the functionality of the PC is compromised. Reason I say this is I am pretty sure I see the same behavior on 2 of my other PCs that do not run the Blue Iris software.
#Blue iris support software#
One thing I do think after all this time is this problem is more generalized than just for this Security camera software I am running (Blue Iris). So what I am doing is every time I notice a change in the "build" of Security Center or Virus scan I retest and post results. Only feedback i have received is very general comments that they are aware of this problem, that it has been reported by numerous users and that it will need a new release to fix this. Message was edited by: lotty on 8/30/12 2:40:45 PM CDTįirst, I do ask if there is a specific fix and or date for a fix every time I interact with this McAfee engineer.
#Blue iris support install#
Now I will uninstall Mcfee, run MCPR.exe cleanup tool, reboot, install Microsoft Security Essentials and wait for McAfee to fix this. Min / InUse / Paged / Nonpaged InUse / Paged / Nonpaged New Test (new v McAfee code) Previous Test (older v McAfee Code) Below is a recap of the timeline from a fresh boot memory use pushes to 7.3GB within 2 hours and causes PC to lock up. PC runs with average INUSE memory of only 2GN of the 8 GB. but its only a guess that McAfee has even attempted any sort of fix with this release … could be just a new footprint of the current releaseįor past couple of weeks I have been running Microsoft Security essentials as a temporary antivirus solution with no issues running constantly with more than 7 days of uptime. I guess best you can say is that it does appear they have slowed the timeline. short answer is same result for McAfee Security Center v 11.6 build 11.6.385 and McAfee Virus scan v 15.6 build 15.6.2. Update – New release of Total Protection out (auto installed on one of my other PCs) so I thought I would install and retest. Also not sure if the original root issue was a McAfee problem but it sure seems McAfee is in the mix of a continuing string of problems. Maybe just sitting over night and some process runs in background or whatever. Not sure if I did anything specific to cause the names resolution to start working again. retested and I could not access the PC with RDP using computer name. I once again tried to establish the trust relationship. while on hold and answer the initial round of quesions from the agent. first thing this morning contacted McAfee support. attempted some arp flushes and IPCONFIG release / renews. Anyway I backed this off since I did not want to have a long term issue It was useful in further identifying the problem as netbios name table issue. Now for me I know this is a hard coded solution that I never had to do before so still points to some root issue I have not figured out. and manually added the computer name and IP address mapping. opened C:\Windows\System32\drivers\etc\hosts. rebooted my router (ATT Uverse) that acts as my DHCP/DNS but this did not help. just would not work when I initiated prompts me for temporary password. i am guessing it could not name resolve the PC. attempted to establish the trust in the mcafee home network defense. All along I was able to see the PC from my networks and see shared drives even when could not RDP with computer name. So seemed to point to netbios name table hosts issue. Verified behavior from 2 PCs RDPing into the problem PC. Then I tried using the IP address and it worked. Still could not access via RDP and computer name than I normally use. So I hooked up monitor and keyboard for direct physical access and uninstalled, cleaned using MCPR and reinstalled. First difference was just powering off and rebooting did not allow my to have immediate access. Going to report this as it has similarities, the problem fixed itself or went away.