We've started rolling out Windows 7 x64 as our new build (replacing XP systems). Not long after getting started on the rollout we've been encountering this error when we go to install a printer driver. It is bizarre in that it does not happen to every system, but it does happen to a significant number of systems. I believe I have found a work around but it just doesn't seem right that this is happening and that we should have to use a workaround. My work around is changing the permissions on the .dat files located at C:\Windows\System32\DriverStore folder. By default these files have System with full control, and users with read. That's all. If we add administrators with full control, then we can install the printer driver without getting the error. But the sad thing is a process or service changes the permissions back on these files.
I'm wondering if we are the only people seeing this? I've googled it and it is not unheard of. It sounds like the problem started with Vista. But why is this happening? Are any of you encountering this problem? Thanks, AJ.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
We've started rolling out Windows 7 x64 as our new build (replacing XP systems). Not long after getting started on the rollout we've been encountering this error when we go to install a printer driver. It is bizarre in that it does not happen to every system, but it does happen to a significant number of systems. I believe I have found a work around but it just doesn't seem right that this is happening and that we should have to use a workaround. My work around is changing the permissions on the .dat files located at C:\Windows\System32\DriverStore folder. By default these files have System with full control, and users with read. That's all. If we add administrators with full control, then we can install the printer driver without getting the error. But the sad thing is a process or service changes the permissions back on these files.
I'm wondering if we are the only people seeing this? I've googled it and it is not unheard of. It sounds like the problem started with Vista. But why is this happening? Are any of you encountering this problem? Thanks, AJ.
Share this post
Link to post
Share on other sites