|
Method 1 – Windows Server 2003 Terminal Services
Firstly, if you’re running into this issue on a Windows Server box running Terminal Services, your problem can be narrowed down to one or two things.The best solution that has worked for most people is to simply uninstall Internet Explorer enhanced security configuration.

If that doesn’t work, another thing you can do is to add the server name to the list of Trusted Intranet Sites in IE.
Make sure to log off and back on in order for it to take effect. If you’re not running a server, read on.//servername
Method 2 – Turn off anti-virus or firewall
If you are having this issue in Windows XP or Windows Vista, then your problem is probably related to an actual permission issue.Norton Internet 200X, Bitdefender, AVG anti-virus, Trend Micro 200X can all cause this problem. If you have any of these programs installed, make sure to disable them and test it you can run programs, open files, etc.
If so, then you’ll have to either use a different program or find something on the Internet about to how to configure your software to not interact badly with Windows.
The same thing can also happen with an overly aggressive firewall. If you are running Comodo firewall or something similar (other than the basic Windows Firewall), then disable that also.
Method 3 – Unblock the file
If neither of those two methods worked, the file may be blocked by Windows. Note that this is only for Windows Server 2003 and higher.When you copy an EXE file from another computer to a Windows Server 2003 box, there is what is called a blocked property set on the file. This is due to the increased security on servers.
Right-click on the file and choose Properties. You’ll see a button called Unblock at the bottom.

Method 4 – Real permissions issue
Finally, you may actually have a permissions issue. In this case, make sure you are an Administrator or you are part of the Domain Admins group if you are in a domain.Also, you can try right-clicking on the file and choose Run As. Then type in the Administrator credentials and try to run the file. If you are able to run it, that means you account is not setup properly or is not in the right user group.
|
Method 1 :
Double-click on the "Windows" folder
Double-click on the "Dllcache" folder.
Locate the Rundll32.exe file, right-click on it and then select "Copy.
Click on the "Back" button in the Windows Explorer to get back to the "System 32" folder.
Right-click any open space and then click "Paste."
- Put the Windows XP CD ROM disk in the CD ROM drive.
- Click Start, and then click Run.
- Type expand X:\i386\rundll32.ex_ c:\windows\system32\rundll32.exe in the Open box, where X is the letter of your CD ROM Drive.
- Restart the computer.
Method 2 :
Go to the "Start" menu.
Go to the "Start" menu.
Click "My Computer.
Double-click on the "C:" drive.Double-click on the "Windows" folder
Double-click on the "Dllcache" folder.
Locate the Rundll32.exe file, right-click on it and then select "Copy.
Click on the "Back" button in the Windows Explorer to get back to the "System 32" folder.
Right-click any open space and then click "Paste."
|
- Start the computer by using your Windows XP CD-ROM. Press any key to boot from the CD.
- After the setup files are finished loading press R to repair using Recovery Console.
- When you are in the recovery console, select the installation to log on to (usually number 1), and then press ENTER.
- Login to the Administrator account by typing the password for this account, and then press ENTER.
- At the recovery console command prompt, type the following command, and then press ENTER:
For Uni-Processor systems:expand <cd-drive>:\i386\ntoskrnl.ex_ <hd-drive>:\Windows\system32\ntoskrnl.exeFor Multi-Processor systems:expand <cd-drive>:\i386\ntkrnlmp.ex_ <hd-drive>:\Windows\system32\ntoskrnl.exeNote In these two commands, the <cd-drive> placeholder represents the drive letter of your CD drive, and the <hd-drive> placeholder represents the drive letter of the hard disk on which windows is installed. - If you receive a prompt to overwrite the file, press Y.
- Type exit, and press ENTER at the command prompt.
|
- Log on to your computer as an administrator.
- Click Start, and then click Run.
- In the Open box, type cmd, and then click OK.
- At the command prompt, typemsiexec.exe /unregister, and then press ENTER.
- Type msiexec /regserver, and then press ENTER.
- Verify that the SYSTEM account has full control access permissions to the HKEY_CLASSES_ROOT hive in the Windows registry. In some cases, you may also have to add Administrator accounts. To do so:Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:322756 How to back up and restore the registry in Windows
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Click the following registry hive:HKEY_CLASSES_ROOT
- On the Edit menu, click Permissions.
- If SYSTEM is not listed in the Group or user names list, click Add, make sure that the local computer name appears in the From this location box, typesystem in the Enter the object names to select box, click Check Names, and then click OK.
- Click SYSTEM in the Group or user names list, and then select the Full Control check box under Allow in the Permissions for SYSTEM box.
- Click Apply, click OK, and then quit Registry Editor.
- Restart the computer. Your problem is resolved.
Subscribe to:
Posts (Atom)