10-24-2013 02:29 AM - last edited on 12-31-2013 12:16 AM by maikoro
After installing OSX 10.9 Maverick, we are now unable to scan from our HP ScanJet 8200 Scanner.
Is there an update coming or is there another way to fix the problem?
P.S. This thread has been moved from Scanners to Macintosh-Compatible Products. - HP Forum Moderator
10-24-2013 09:52 AM
10-24-2013 12:30 PM
I have the same issue:
"An error has occurred saving the file because it could not be written to. Check the properties for the file to make sure it is not read-only."
I just installed Mavericks- now the scanner (HP ScanJet G3010) will scan, but not save files. 1) Are you gong to release a Mavericks driver- Crazy that that has not already been done! 2) How do i just set up my scanner without HP software, I could then maybe save uisng Scanners & Printers. 3) The scanner is not recognized in Scanners & and printers- therfore i cant use preview or images to scan. 4) Your tutorials do not work and/ or are not related. ...
Here is my thinking...If I can get Scanner to show up in Scanner and Printers I could try a different way to scan!
10-29-2013 07:19 AM
Same here, Scanjet 4370, fresh OSX 10.9/Mavericks install. Print black lines, error on saving.
Just the same chaos after update to 10.7/Lion.
Please update your HP Scanjet software!!!
11-02-2013 09:13 PM
After installing OS X 10.9 Mavericks cannot use my HP Scanjet 4670. It says the software COL10842b is PowerPC and its no more compatible. Is there any scheduled update coming? I hope so, it is a wonderful hardware that vertical transpartent scanner.
11-06-2013 12:04 AM
HP Scanjet 5590 does scan an image or a document. The image got saved as a greyscale striped picture. The document could not be saved. It gave an error regarding a protected file.
The error persisted after repairing the harddrive. The scanner worked perfectly under Mountain Lion.
11-07-2013 05:14 AM
I have a ScanJet G3110. Worked perfectly under 10.8. Maverick upgraded impacted the scanner as discribed in earlier posts, file write permission errors and black/white bars.
Any idea when HP or Apple will have a fix?
11-09-2013 09:56 PM
I'm using a G3010 Scanjet and get exactly the same problem since updating to Mavericks.
Does anybody from HP read this very forum thread? We all would appreciate some kind of reaction / answer to our problems!
Thanks in advance!
Attached are two screenshots: a scanned form as seen on screen, and as seen after saving as JPEG
11-13-2013 01:47 AM
After installing Mavericks I cannot scan anymore with my ScanJet 8200. How do we know HP will bring out an update of the software in the near future? I made a subscription for the announcement of new updates and releases for this product but the uncertainty factor is that I do not know that HP is working on the issue, nor if they will fix the problem. Is HP aware of this issue? How do we inform HP?
11-15-2013 01:58 PM
I found a workaround in a pinch to get a scan out of my Scanjet 4850 while using Mavericks 10.9. It's not ideal, but when you're desperate, it's better than nothing.
I went to System Preferences and clicked on HP Scanjet 4800, which brought up shortcuts to the scanner front panel buttons. By default, the one assigned to the first button is "Open in Preview", so I pressed that button on the scanner, and it scanned the image I needed and opened it in Preview.
There are several shortcuts you can choose from, but I only tried "Open in Preview". It created a 200 dpi RGB JPEG, which was plenty to work with in my particular situation.
By the way, I had to quite out of the HP Scanjet software for it to work.
Hope this helps someone out there.
11-16-2013 09:57 PM
I applied the same process to my G3010 scanner and was able to scan and save images :-)
Like you, users do a better job than HP: there is still no info about Mavericks compatibility in their whole support website.
11-26-2013 09:23 AM
My Scanjet 8300 no longer works with OS X 10.9. It scans but will not save. I have tried every workaround to no avail. Unfortunately I use this scanner daily for my magazine. This is a huge problem for me. Hopefully you will get this bug fixed quickly!