Vista - Problems installing scan drivers Epson Perfection V500

Just purchased Perfection V500 Can't install scan software. I get an error " Could not copy File" "Check the setup disc then run setup again C:\User\Appdata\Local\Temp\\setup.ini
I'm running an HP PC Core Duo Quad Q6600, 4 GB RAM, Vista Home Premium 64 bit SP1. Spent 1.5 hours on the phone with Epson yesterday until tech said he had done everything he had on his troubleshooting checklist then put me back on hold for another tech and ended up back on hold. Anyone have an idea? This is my first problem with Vista. I was hesitant to get involved with it in the first place. Epson promotes the scanner as compatable with Vista 64. And I have seen posting that indicate success for others running the scanner. Thanks

Just go to the Temp Folder in C:\User\*Your user name*\Appdata\Local\Temp rigth click on it, select properties and check out the read only box

Try downloading a newer driver from the Epson website and using that. Even if it is the same version.

[quote=gjmill;684217]Just purchased Perfection V500 Can't install scan software. I get an error " Could not copy File" "Check the setup disc then run setup again C:\User\Appdata\Local\Temp\\setup.ini

I am having exactly the same problem, I've tried to re-install quite a few times but always with the same result "Could not copy files...."

I'm hoping somebody might have some other ideas as the ones on this thread have not worked.

I recently purchased a V500 and despite literally hours on the phone with Epson, they could not get it to install. They say that Windows refuses to recognize the info from the port.

I also had trouble w/ the scan feature of my All in One HP printer, because Vista Basic does not support scan/fax capability. Adobe Photo Elements got me the scanning capability.

It galls me though to think I'm moving up from Windows XP home and find out that the Vista Home won't do things the XP would. I had to install my scanner on my kids (XP) computer.

Any advise would still be appreciated. It's still an on-going issue.