How To Fix “The Requested Operation Requires Elevation” Error

Windows 7 logo

While executing some commands in Windows 7 (or Windows Vista) command prompt, you may see some error message like

The requested operation requires elevation

This may also appear sometimes when you are installing some older applications in your Windows 7.

In my case the above error popped in while I was trying to run a “netstat –b” command from the Windows 7 command prompt. You may also end with the same error if you try to other commands like “ipconfig /flush” or “ipconfig /release” etc.

requested operation requires elevation error

This error arises so because, some programs like this need to be run with elevated privileges even though you did turn off UAC (User Account Control). However, there is a simple solution available for this, all you need to do is that run the command prompt with administrative (elevated) privileges.

Solution:

To solve this error, go to Start > Type cmd in the search box, you will the result cmd.exe under programs. Right-click on it and select Run as administrator.

run_cmd_administrator_1

Now run the same command and you will no longer get any error messages and the command gets executed in the right manner.

Command prompt with elevated administrator rights

If you are wondering so as to how to find whether you are running the command prompt with Administrator privileges or not, use the following hint:

If you are running command prompt as an admin, you will see the word “Administrator” in the CMD window title. Checkout the following screenshot, which depicts the difference between the two CMD windows.

Difference between the command prompt windows

How To Deal With “Firefox is already running..” Error ?

You might have observed this error message many times while trying to open Firefox too soon after it was closed or may be due to closing Firefox abnormally (without deleting the lock file) or not shutting down the Firefox properly or when your Mozilla can’t find profile folder in the expected location

“Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.”

Firefox not responding

An article in Firefox Knowledge Base explains why this error occurs:

This error can occur in Firefox 3 because of a delayed shutdown, if you try to reopen it too soon after it was last closed

Solution 1 : End processes

The one popular and easiest solution to this is to kill the process in the Windows task manager.To do this right click on your Windows taskbar and choose “Start Task manager”.

start task manager

Locate the process called “firefox.exe” (each instance of Firefox when running multiple pages) in under the processes tab:

processes in Task manager

Right click on the process and choose “End Process” or simply use “delete” from your keyboard.

End a process in Task manager

And now re open Firefox browser and it’ll also recover tabs from your last session that you have just ended abruptly by stopping the firefox.exe process.

Solution 2: Remove the profile lock file

This requires finding the location of the Firefox profile in your computer and deleting the lock  files under your profile.

Step 1 :

Press Windows+R button to open run command prompt, type “appdata” and click ok

appdata run command


Step 2:

Now a windows explorer window will open up then navigate to the following folder by the give paths:

C:\Users\<user name>\AppData\Roaming folder  — Windows 7 and Windows Vista

C:\Documents and Settings\<user name>\Application Data folder – Windows XP and Win 2000

Navigate to Mozilla >Firefox >Profiles from there

Step 3:

Delete the file “parent.lock” from your profile folder.

parent lock firefox profiles

via [Matt Cutts]

Note:

The methods given here are exclusively for Windows based systems.

Note that this will only solve the current issue with Firefox, however we can’t guarantee that Firefox will not behave like this in future.

WordPress 2.8.5 – Security Hardening Release is Out

Popular Blogging Platform WordPress has released the update to the earlier version as WordPress 2.8.5 terming it as the “Security Hardening Release” with the following changes:

    • A fix for the Trackback Denial-of-Service attack that is currently being seen.
    • Removal of areas within the code where php code in variables was evaluated.
    • Switched the file upload functionality to be whitelisted for all users including Admins.
    • Retiring of the two importers of Tag data from old plugins.

WordPress 2.8.5 Download wordpress logo

The Issues:

Many bloggers today have reported some minor issues while upgrading to version 2.8.5

An error message

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2354671 bytes) in …”

was prominent among the issues raised by the bloggers.

The fix to this issues is pretty much simple:

First disable all your plugins while upgrading and revert to the default theme of WordPress.

Now perform the auto-install upgrade to WP version 2.8.5.You’d have a very smooth upgrade.Now try to enable all your desired plugins.Now you may find that some plugins are still causing the above said error message.

Here’s the fix for it:

Open your FTP client, and open wp-config.php file in your WordPress installed directory.Add the following line:

define('WP_MEMORY_LIMIT', '64M');

This would increase the amount of memory that is being consumed by the PHP script.

    • A fix for the Trackback Denial-of-Service attack that is currently being seen.
    • Removal of areas within the code where php code in variables was evaluated.
    • Switched the file upload functionality to be whitelisted for all users including Admins.
    • Retiring of the two importers of Tag data from old plugins.