Fix: ERROR_SET_POWER_STATE_VETOED (0x474)

Uninstall the conflicting application or driver

Reading time icon 4 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

fix ERROR_SET_POWER_STATE_VETOED

The ERROR_SET_POWER_STATE_VETOED system error, with code 1140 (0x474), appears when an application or driver prevents Windows from changing its power state, i.e., sleep, hibernate, or shutdown.

The error message reads, An attempt to change the system power state was vetoed by another application or driver, but it doesn’t tell us anything about the app or driver that caused the error in the first place. So, troubleshooting may take some time!

Before you proceed, restart the PC, disconnect all non-critical peripherals, and install any pending Windows updates. For many of you, these quick checks alone should fix the error!

How can I fix ERROR_SET_POWER_STATE_VETOED?

Tip icon Tip
For a quick resolution, check the crash logs in Windows generated around the same time the error appeared on your PC, identify the faulty components (driver or application), and directly head to the relevant solution below. If that’s not possible, follow them in the listed sequence.

1. Terminate active applications

  1. Press Ctrl + Shift + Esc to open the Task Manager.
  2. Now, select the active third-party applications individually and click on End task.task manager
  3. After terminating each app, verify whether the error message goes away.
  4. Once it does, the app last terminated was causing ERROR_SET_POWER_STATE_VETOED (0x474).

2. Uninstall conflicting apps

  1. Press Windows + R to open Run, type appwiz.cpl in the text field, and hit Enter.
  2. Select the conflicting app from the list, and click on Uninstall.uninstall to fix ERROR_SET_POWER_STATE_VETOED
  3. Follow the on-screen instructions to complete the process.
  4. Restart the computer and check for improvements.

If the problem persists after a quick removal, the app may still have some leftover files triggering the 1140 (0x474) error. In this case, I recommend using a top-rated software uninstaller for Windows to get rid of any remnant app cache or Registry entries.

3. Reinstall the malfunctioning driver

  1. Press Windows + X to open the Power User menu, and select Device Manager.power user menu
  2. Look for devices with a warning sign (yellow exclamation mark) listed next to the icon. These are the devices with a corrupt driver and the categories they are listed under auto-expand on the opening the Device Manager.
  3. If you find any, right-click on the entry, and select Unistall device.uninstall driver to fix ERROR_SET_POWER_STATE_VETOED
  4. Tick the checkbox for Attempt to remove the driver for this device, and click Uninstall.confirm uninstall
  5. Restart the computer, and Windows will automatically reinstall a fresh copy of the driver.

4. Update the affected driver

  1. Press Windows + R to open Run, type devmgmt.msc in the text field, and hit Enter.
  2. Expand all the entries here, right-click on the devices listed underneath individually, and select Update driver.update driver to fix ERROR_SET_POWER_STATE_VETOED
  3. Click on Search automatically for drivers and wait for Windows to install the best locally available version.automatic driver search
  4. After updating all the drivers, restart the computer and check for improvements.

If you were able to find the conflicting one in Windows error logs, simply update that driver instead of all the installed ones. In case Windows tells you that the best driver is already installed, head to the manufacturer’s website, find out the newest version, and then manually install the latest driver!

5. Repair the corrupt system files

  1. Press Windows + S to open Search, type Command Prompt, and click on Run as administrator.command prompt
  2. Click Yes in the UAC prompt.
  3. Paste the following DISM commands individually and hit Enter after each: DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth
  4. Now, run the SFC scan using this command: sfc /scannowsfc scan to fix ERROR_SET_POWER_STATE_VETOED
  5. Finally, reboot the PC and check for improvements.

In a few cases, the ERROR_SET_POWER_STATE_VETOED Windows system error was caused by corrupted system files. Here, simply running the SFC (System File Checker) and DISM (Deployment Image Servicing and Management) scans should replace the protected system files with their cached copy.

6. Disable fast startup

  1. Press Windows + S to open Search, type Control Panel in the text field, and click on the relevant result.
  2. Click on System and Security.control panel
  3. Now, click on Change what the power buttons do under Power options.
  4. Click on Change settings that are currently unavailable.power options
  5. Untick the checkbox for Turn on fast startup and click on Save changes. turn off fast startup to fix ERROR_SET_POWER_STATE_VETOED
  6. Finally, restart the PC and verify whether the ERROR_SET_POWER_STATE_VETOED 1140 issue fixed

7. Perform a system restore

  1. Press Windows + R to open Run, type rstrui.exe in the text field, and hit Enter.
  2. Select the Choose a different restore point option, and click Next.restore to fix ERROR_SET_POWER_STATE_VETOED
  3. Pick the oldest restore point from the list and click Next.oldest restore point
  4. Verify the restore details, click on Finish, and then confirm the change.
  5. Wait for the process to complete. It may take 15-45 minutes.

A system restore allows you to revert the PC to a previous stable state where the ERROR_SET_POWER_STATE_VETOED issue didn’t exist. All you need is a restore point created before the issue first appeared!

In case a restore point is not available, the last option is to reinstall Windows. For that, get the Windows ISO from Microsoft’s official website and then proceed with the reinstallation.

For any queries or to share which fix worked for you, drop a comment below.

More about the topics: event log viewers, System Errors

User forum

0 messages