HP support says my webroot is not compatable with my Windows 7 and that is why my HP printer will no

Hello BobYanchus
 
Welcome to the Webroot Community,
 
Webroot is compatible but have a look below,
 
Please have a look here at these PC User Guide articles that can help you with unblocking and allowing if you are totally sure these programs or sites are not malicious.
 
Controlling active processes
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C10_SystemControl/CH10b_ControllingPr...
Blocking/Allowing files
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C5_Quarantine/CH5b_BlockingAllowingFi...
Managing protected applications
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C6_IDProtection/CH6c_ManagingProtecte...
 
 EDITED:
Managing active connections
http://www.webroot.com/En_US/SecureAnywhere/PC/WSA_PC_Help.htm#C4_Firewall/CH4c_ManagingActiveConnec...
 
 
Lets try to put into English the essence of the areas where a user can tailor what WSA does to protect the system
 
There are essentially 3 key areas where this can happen/a user can override WSA.  These are essentially reached, from the main WSA panel, as follows:
 

1. PC Security > Block/Allow Files
2. Identity Protection > Application Protection
3. Utilities > System Control > Control Active Processes

 
and once there the user usually has the options to:
 
A. "Allow"
B. "Protect/Monitor"
C. "Block/Deny"
 
In the case of 1. Detection Configuration
 
If an item is set to:
 
- "Allow", WSA ignores it during scans and shield actions, meaning if it's a virus that has been allowed, it can continue acting as a virus acts.  Be careful of what you allow in this area and ensure it's something you trust implicitly if you are going to change the status from Block to Allow.
 
- "Monitor", WSA will watch the item to determine if it is legitimate or related to malware.  It is not necessary to add files into this list or set files to monitor manually unless you are changing them from a Block or Allow status.  This might be useful if for example you think Webroot might have had a false positive on something and you want to check again at a later time to see if the determination has changed.  You could set it to Monitor and have Webroot check it again.
 
- "Block", then WSA will treat the items as it would detected malware.  It will not be executed, and it will not be written to your hard drive.  Detected infections are automatically set to a Block status.
 
In the case of 2. Protected Applications (Internet Security & Complete version ONLY)
 
In this case:
 
- "Allowed applications" are not secured against information-stealing malware, and also have full access to protected data on the system. Many applications unintentionally access protected screen contents or keyboard data without malicious intent when running in the background. If you trust an application that is currently marked as "Deny," you can change it to "Allow."
 
- "Protected applications" are secured against information-stealing malware, but also have full access to data on the system. By default, web browsers are assigned to the "protected" status. If desired, you might also want to add other software applications to "protected," such as financial management software. When you run a protected application, the Webroot icon in the system tray displays a padlock.
 
- "Denied applications" cannot view or capture protected data on the system, but can otherwise run normally.
 
And finally, in the case of 3. Control Active Processes
 
If a process is set to:
 
- "Allow" it means WSA allows it to run on the system. It's important to note that if an item is already allowed here, that's because Webroot knows already from seeing the file before that it's ok to allow.
 
- "Monitor" status means WSA will journal what that program is doing and keep a very close eye on it for any suspicious activity.  Basically it would treat it as if it wasn't already sure about it one way or the other, and it wants to monitor it closely until it's sure about it.
 
- "Block" means just that...iWSA does not allow it to run on the syste.  Be very careful about what you block in this area and ensure that anything you decide to block is a non-essential process.  Otherwise, you could be setting yourself up for a lot of grief if you block something critical.
 
Now, hopefully that has given you a consolidated low down on where to look and what you can do to affect how WSA 'interferes' with files, objects & processes on your system...and so wil help you get to the bottom of what is causing you grief.
 
Do post back with any specific questions that you may have re. the above.
 

Hi BobYanchus
 
Welcome to the Community Forums.
 
Well, unless you are using a very old version of Webroot, i.e., something other than Webroot SecureAnywhere that his prior to 2011, then I would be very surprised by that statement as I ran WSA under Win 7 with no issues.
 
Can you advise as to the exact title of your Webroot software and the version no.?
 
As to the black type issue I have not heard of WSA preventing black type printing specifically so I would expect that to be an issue with the printer itself.
 
Regards, Baldrick

Webroot Security Anywhere.  
This problem with photosmarts not printing black is all over internet so paying for another security system did not seem to be a printer malfunction solution.

Hi BobYanchus
 
Have to say that if you are running WSA, and you are running the latest version which is v9.0.8.81 then it will most certainly be compatible with Windows 7...so I would ahve to sayt that HP are talking out of their posterior...please ask them for specifics as to why they think that...they should put up or shut up. ;)
 
As for the non black printing with an HP 5220...well, I have one too and it seems to be printing black type with absolutely no issue at all. I have heard of WSA blocking printer COMPLETELY...but never of it blcoking one print colour, i.e., black. Can you print in colour?
 
Regards, Baldrick

Yup, no prob with color printing, have used most of it up after running diagnostics again and again.  

I suspect that the nozzle for the black ink is bunged up...have you tried a blast of compressed air up it or blowing at it with a straw (making sure that you protect yourself with a piece of paper towel or the like due to potential blowback)?