A
Anteaus
On computers where IE8 has been installed we're getting 'Publisher could not
be verified' warnings when launching executables from a fileserver's readonly
share.
The irony of it is that we don't even use Internet Explorer, we use Firefox.
Thus we haven't updated IE until now, and are only doing so because of one
awkward site which won't open in FF. But, the presence of IE8 is now having
an adverse effect on NON-Internet use of the computer.
There are several Internet pages offering fixes for this, but all seem to
have drawbacks such as reducing Internet-zone security, or labor-intensive
work such as the need to adjust Group Policy on a user-by-user basis. So far
I can find no entirely satisfactory fix.
e.g.
http://tinyurl.com/ycqcqll
http://tinyurl.com/ybkcaje
http://tinyurl.com/yhtga59
The key problem seems to be that the system now treats shares as being
Internet-zone resources instead of LAN resources. Which would seem to be a
coding blunder, I'm thinking.
Does anyone know of a reliable, side-effect free way to nail this bug? If
there was a HKLM (and NOT HKCU) registry fix that would be best as it could
be applied quickly and easily via a .reg file, and would do the job once and
for all.
be verified' warnings when launching executables from a fileserver's readonly
share.
The irony of it is that we don't even use Internet Explorer, we use Firefox.
Thus we haven't updated IE until now, and are only doing so because of one
awkward site which won't open in FF. But, the presence of IE8 is now having
an adverse effect on NON-Internet use of the computer.
There are several Internet pages offering fixes for this, but all seem to
have drawbacks such as reducing Internet-zone security, or labor-intensive
work such as the need to adjust Group Policy on a user-by-user basis. So far
I can find no entirely satisfactory fix.
e.g.
http://tinyurl.com/ycqcqll
http://tinyurl.com/ybkcaje
http://tinyurl.com/yhtga59
The key problem seems to be that the system now treats shares as being
Internet-zone resources instead of LAN resources. Which would seem to be a
coding blunder, I'm thinking.
Does anyone know of a reliable, side-effect free way to nail this bug? If
there was a HKLM (and NOT HKCU) registry fix that would be best as it could
be applied quickly and easily via a .reg file, and would do the job once and
for all.