Here is what I have found so far.
We are running Vista on all of our clients, and have been told by adobe that Acrobat 8 is designed to run on Vista. We have seen this problem on a variety of platforms including laptops and desktops, regardless of the client OS. There is no indication for a connection to the video hardware, as we see this on nVidia, ATI, and even some older type cards. We have also reasonably confirmed that it is not likely a corruption of any of the installed files... removing all of the installed files from ALL directories and reinstalling does not eliminate the problem. Same thing for the registry entries. So what is left?
We believe that the problem lies firmly in the files installed by Adobe Acrobat that deal directly with the writing and gathering of information written to the registry. Our developers feel that this would explain almost all of the problems being reported here. Adobe has written their dlls specifically in this way.
We have been corresponding separately with Jeff Moran, however like the rest of the group reporting on this issue, we have seen little actual support for the issue. We have a number of commitments for contacts with engineering (theirs to ours), however this has thus far not happened. His voice mail says that he is out until the 8th of Jan. Our team of developers can not take the issue much further than what we have outlined, as we do not have access to the internal workings of the program, so our only recourse at this point is to either wait for Adobe to rectify the issue (hopefully the developers will be back off of vacation to start working again) or start motivating management to move it along using fiscal measures. I have to think that a substantial problem like this with customers seeking remuneration and/or moving to a competitive product HAS to get their attention.
If anyone has any productive thoughts as to a resolution given these circumstances, I know that we would be thrilled to hear them, as I am sure the rest of the forum would. Aside from this, we are regrettably at the mercy of the engineers, not tech support, to solve this issue.
Happy Holidays,
Jeff MacMillan