F
Fred Yarbrough
Lately two of our Windows 2003 Active Directory Domain Controllers are
getting the following message when they are logged into.
___________________________________________________________
Security Alert!
The driver software that you are installing for:
memNT Driver
has not been signed with Authenticode (TM) technology. Therefore, Microsoft
cannot tell if the software has been modified since it was published. The
publisher's identity cannot be verified because of a problem:
The third-party INF does not contain digital signature information.
Do you still want to install this driver software?
_____________________________________________________________
We keep selecting NO, but this prompt keeps coming up with each logon.
There is a file called memNT.sys that is located in the
Winnt\system32\drivers folder. It shows up as being a Microsoft file in the
properties.
The only thing that has been installed on these machines is the normal
Microsoft Critical Update patches. I am suspecting that one of the patches
has caused this warning but I cannot find anyone else who has seen it. Any
Ideas?
Thanks,
Fred
getting the following message when they are logged into.
___________________________________________________________
Security Alert!
The driver software that you are installing for:
memNT Driver
has not been signed with Authenticode (TM) technology. Therefore, Microsoft
cannot tell if the software has been modified since it was published. The
publisher's identity cannot be verified because of a problem:
The third-party INF does not contain digital signature information.
Do you still want to install this driver software?
_____________________________________________________________
We keep selecting NO, but this prompt keeps coming up with each logon.
There is a file called memNT.sys that is located in the
Winnt\system32\drivers folder. It shows up as being a Microsoft file in the
properties.
The only thing that has been installed on these machines is the normal
Microsoft Critical Update patches. I am suspecting that one of the patches
has caused this warning but I cannot find anyone else who has seen it. Any
Ideas?
Thanks,
Fred