Before I get into it, I must admit it's not clear if refilled cartridges work or not. I think we have just some anecdotes that they don't but it could be isolated cases. So HP's claims there might have merit.
Now that that's over with, I want to draw your attention to this gem that caught my eye from HP's statements:
We updated a cartridge authentication procedure in select models of HP office inkjet printers to ensure the best consumer experience and protect them from counterfeit and third-party ink cartridges that do not contain an original HP security chip and that infringe on our IP,
This is amazing when you break it down. First of all you have this reasonable part:
We updated a cartridge authentication procedure in select models of HP office inkjet printers to ensure the best consumer experience and protect them from counterfeit and third-party ink cartridges
So far so good. Without any context it seems a reasonable enough statement.
The use of "that" here, though, indicates they are talking about a specific subset of counterfeit or third party ink cartridges (or that they believe all of them fit the following criteria). This is where they shoot themselves in the foot I think.
do not contain an original HP security chip
So, in other words, they are requiring you to only buy cartridges with their DRM in order to ensure you only buy cartridges with their DRM. Great circular logic there. But the best part is next:
and that infringe on our IP,
Why do they infringe? Because big companies have lobbied for laws to give themselves more power when it comes to their IP, and its these laws that give HP the authority to do what they do (as opposed to laws that might protect creators of competitive products). So HP's reasoning here is because it's legal, they're gonna do it. So if you strip away will the corporate speak, their OFFICIAL statement is not too far from that they're doing it because they thought they could get away with it.
Doesn't seem to be a problem from that angle at least. Sounds like FUD.
The update has the bad habit of reverting settings that you specifically configured, and persisting settings that should be reverted. For example, if you use other virtualization solutions, you probably turned Hyper-V off since there's conflicts. The update turns it back on for some reason without telling you which can really mess you up. Next, Fast Startup is re-enabled even if you disabled it because it's broken (which it is for me). Lastly, Cortana is designed to be enabled all the time with this update, and the UI switch to disable it is gone. The problem is it should turn itself back on, otherwise it is difficult to determine how to do it without the UI. Sure, keep the registry setting so users who want to risk going into unsupported territory can keep turning her off, but the update really should switch things back to supported territory...
"I have five dollars for each of you." -- Bernhard Goetz