![]() ![]() My apologies folks! The non-booting APC_INDEX_MISMATCH error still exists with the WFBS Services product on my Win 10 computer. They told me that there would be a fix out for this issue by 10/1/16, and I see that my agents are now at, but I have not had time to do a crash test on boot with that box checked again. I got around that problem by booting into safe mode and renaming the Trend Micro folder, then booting normally, renaming the folder back again, starting the services, starting the agent, UNchecking the "Enable program inspection to detect and block compromised executable files" box and updating the agent. If your agent was, and you had the Behavior Monitoring ransomware protection "Enable program inspection to detect and block compromised executable files" box checked and you had Win 10, you MIGHT have gotten a non-boot situation, requiring a system restore. really dont want to do another restore!I have been working with Trend for the last week or so on issues with the agent and one Win 10 system. It doesnt suprise me that i would need to add system utilities like those as exceptions, ive seen stranger issues with office scan behavioral monitoring causing issues with legitimate products (like outlook!) after an update. 'approved programs/exceptions' list under behavioral monitoring settings and the 'anomaly' issue went away for me. Thanks for the tip GrandVizir, i added the path for both powershell.exe and cmd.exe to the it actually BSoD'ed me yesterday after rebooting to apply the latest update to my officescan agent, to the point where i had to do a restore from a local backup image. Snipi was also seeing this issue on my windworkstation. ANOMALY: use of REX.w is meaningless (default operand size is 64) If I unload WFBS Services, close the cmd prompt and re-open it, then ping, it gets normal output. ANOMALY: use of REX.w is meaningless (default operand size is 64)" after every command. Open a command prompt and run any command, such as pinging 8.8.8.8 and see the output. They also appear to have pushed an update for their WFBS Services product, and it comes with a new twist. I opened a case with Trend this morning and provided the engineer with some logs from a desktop and the server. ![]() The same message with OfficeScan Antivirus is also being logged. All devices tested have 6125 installed.īesides the errors shown in Action Center every 3 minutes or so, the Application Log on the desktop is full of the following errors:Įrror while updating Trend Micro OfficeScan Anti-spyware status to SECURITY_PRODUCT_STATE_ON (error BA060000). Other Windows 10 (or server OS) didn't throw the same message. It seems to only happen on Windows 10 devices with AU installed though. The error comes back as soon as OfficeScan is back up running. I have just unloaded OfficeScan and confirmed the message goes away. I also noticed the issue in the command prompt yesterday, but didn't think it was related to Trend. The agents are now showing version 6125 but the console still shows 6054. The MS updates had to be downloaded/installed manually as the AU broke Windows Update service on the desktop, amongst other services. I have also installed Microsoft patches KB3176936 and KB3176938 with no luck. ![]() ![]() Yesterday I installed the 6125 patch for OfficeScan (applied 6054 first), but I am sad to say it has made no difference to the issues I am facing with Windows 10 post AU. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |