Tag: Windows

IE7 “The publisher could not be verified” while running executable from network

Ik had een probleem bij een klant waarop een xp pc de volgende melding verscheen:
Publisher Could Not Be Verified
Publisher Could Not Be Verified

 Oplossing:

When you are trying to run an executable located on another machine on your network, running Windows XP SP2 or higher, you are accosted with a prompt: “The publisher could not be verified”. You are forced to confirm that you wish to run this program… every time you run it.

You can disappear this message by setting the following Group Policy Object (GPO)

Go to User Configuration >> Administrative Templates >> Windows Components >> Attachement Manager and add “*.exe” to the “Inclusion list for moderate risk file types” setting.

“This policy setting allows you to configure the list of moderate risk file types. If the attachment is in the list of moderate risk file types and is from the restricted or Internet zone, Windows prompts the user before accessing the file. …”

In other words, this allows you to run an .exe from the Intranet zone without a prompt, but it will warn before running one from the Internet. A lot of people are instructing to add *.exe to the list of low-risk file types. Doing so, you are allowing .exe files to execute from anywhere on the internet.

 

Vista & Grabit

Disabling Data Execution Prevention (DEP)
Data Execution Prevention is a security feature that can be a bit of a pain at times. Often things will simply appear not to run at all; hopefully you will notice a bubble from the taskbar letting you know that DEP is the cause. If Vista (and actually this has been around since Windows Server 2003) sees that a process is being spawned that “could” be unwanted, DEP shuts it down. This is especially common in some application installations: if a Windows Installer setup (MSI) calls an executable in Vista, DEP could very well put a stop to it. If you are trying to run an installation or other executable being stopped by DEP, it could save you some trouble so turn it off while you attempt to give it another shot…

Run a command prompt as administrator. From the start menu, select “All Programs”, then “Accessories” and right-click on the “Command Prompt” shortcut and choose “Run As Administrator”. From here you can use the following command to disable Data Execution Prevention (DEP) with the following command:

bcdedit.exe /set {current} nx AlwaysOff (Dit was de oplossing)

Keeping your command prompt open, run your setup or other process being stopped by DEP. Then, to turn it back on again, do the same and run the following:

bcdedit.exe /set {current} nx AlwaysOn

Translate »