This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After the 24H2 updates the HP Scanner 2000s2 and the N4000 series scanners will not work. It all happened when the host USB drivers updated. Has anyone had this issue and if so do you have a fix. All scanners in our school district were working great until the 24H2 was pushed out.
Any suggestions would be appreciated.
Thank you.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
According to Microsoft, the December 10th KB5048667 update fixed the issue:
https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2
Please post if this update did succeed in fixing your scanner. Testing on one of our computers at a location right now.
Looks like this affected WIA drivers too but, not just TWAIN. Have a similar problem with TWAIN drivers for Fujitsu Fi-7160 and 8170 scanners with the 24H2 Windows 11 build.
Please share your results. We are going on way too long with only a few people who are able to scan (because their OS hasn't updated yet). But a lot of people who can't and we need to keep things up to date.
I have the same problem. I did fix it by rolling back the update, but in our firm we must have everything up to date so an update from microsoft that resolves this issue would be wonderful.
I will try to re-install the drivers tomorrow and update this message with the results.
Unfortunately not. I know that level 2 said level 3 were working with Microsoft on an update but I don't think this Tuesday update did much to fix the issue but level 2 said rolling back the computer to 23H2 may fix the issue....but we are not going to do that and just hope HP and Microsoft realize how urgent his issue is for many businesses including the medical sector.
