ERROR_THREAD_WAS_SUSPENDED (Error Code 699) [Solved]
Disabling sleep mode and fast startup worked for most
4 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
The ERROR_THREAD_WAS_SUSPENDED Win32 system error, with code 699 (0x2BB), appears when a suspended thread is terminated. This usually happens after you wake the PC from sleep and is caused by corrupted system files, misconfigured boot settings, and conflicts triggered by third-party apps.
The message for Error Code 699 reads, {Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.
Before you proceed to the solutions, restart the PC, install pending Windows updates, and disable any active performance optimization or third-party antivirus software!
How can I fix ERROR_THREAD_WAS_SUSPENDED in Windows?
1. Repair corrupted system files
- Press Windows + S to open Search, type Command Prompt, and click on Run as administrator.
- Click Yes in the UAC prompt.
- 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
- Now, execute this command to run the SFC scan:
sfc /scannow
- Restart the computer to apply the changes.
In most system errors including Error Code 699 (ERROR_THREAD_WAS_SUSPENDED), corrupted system files emerge as the underlying cause. So, you must run the DISM (Deployment Image Servicing and Management) and SFC (System File Checker) scans to replace all problematic files with their cached copies!
2. Reconfigure settings to never put the computer to sleep
- Press Windows + S to open Search, type Control Panel in the text field, and click on the relevant result.
- Click on System and Security.
- Click on Change when the computer sleeps under Power Options.
- Choose Never for Put the computer to sleep under both On battery and Plugged in.
- Click on Save changes, then reboot the PC and verify whether ERROR_THREAD_WAS_SUSPENDED is fixed.
3. Disable fast startup
- Open the Control Panel, and click on System and Security.
- Click on Change what the power buttons do under Power Options.
- Click on Change settings that are currently unavailable.
- Now, untick the checkbox for Turn on fast startup, and click on Save changes.
- Finally, restart the PC and check for improvements.
Fast startup is a feature designed to boot Windows faster, but it’s often found to trigger conflicts and lead to issues like ERROR_THREAD_WAS_SUSPENDED (0x2BB). So, you will have to disable fast startup!
4. Uninstall conflicting apps
- Press Windows + R to open Run, type appwiz.cpl in the text field, and hit Enter.
- Select any app that was installed, updated, or reconfigured around the same time you first encountered the system error, and click Uninstall.
- Follow the on-screen instructions to complete the process and then restart the PC.
- If the error persists, uninstall other similar apps from the list.
When a quick removal doesn’t work, it’s likely that the app left behind files or Registry entries that conflict with Windows. So, I recommend using a top-rated software uninstaller to wipe all traces of the app!
5. Reinstall Windows
If nothing else helps fix ERROR_THREAD_WAS_SUSPENDED, the last option is to reinstall Windows from scratch. Given the possibility of data loss, I would suggest moving any critical files to an external drive beforehand.
To reinstall Windows, go to Microsoft’s official website > download the Media Creation Tool > use it to create a bootable USB drive > connect the bootable USB to the affected PC > change the boot order to the flash drive > load the Windows setup > complete the installation.
Since ERROR_THREAD_WAS_SUSPENDED is a software-based problem, a Windows reinstall will certainly fix it. If not, you should contact Microsoft’s official support for more help.
Before you leave, find out the common Windows errors and their solutions and take suitable measures to prevent such issues from reappearing!
For any queries or to share more fixes with our readers, drop a comment below.
User forum
0 messages