As you know the Windows 10 operating system is has a lot of features and some of them are related to turning off your computer in different ways in order to save power at different levels. These particular features are Shut down, Restart, Hibernate, and Sleep. However, there are times when you might encounter some issues when using any of the aforementioned features. One of these issues is when your computer shuts down instead of going to Sleep.
This issue could be caused by several factors including a bug related to the Intel Management Engine Interface or IMEI driver as well as any misconfiguration in the power settings of the BIOS or UEFI. If your computer is going through this problem, read on as this post will guide you in fixing it.
There are several potential fixes you can try to fix the problem. You can try to check the Sleep Advanced Settings or run the built-in Power troubleshooter or run the Power Efficiency Diagnostic Report. In addition, you can also try to troubleshoot the problem in a Clean Boot State or reset or update the BIOS.
The next thing you can do is to run the Power troubleshooter. To do so, follow these steps:
The issue with Sleep Mode might be caused by some third-party programs installed on your computer. This program might be the one that puts your computer to sleep and so to isolate this possibility, you have to put your PC in a Clean Boot State using the steps below.
You could also try to run the Power Efficiency Diagnostics Report to fix the problem. This tool is helpful and will help you analyze the status of the battery but note that this can be quite overwhelming especially if you’re not well-versed in this matter.
Updating the BIOS can help you fix the ATTEMPTED_WRITE_TO_READONLY_MEMORY BSOD error but as you know, BIOS is a sensitive part of a computer. Even though it is a software component, the functioning of the hardware depends on it largely. Thus, you must be careful when modifying something in the BIOS. So if you don’t know much about it, it’s best if you skip on this option and try the other ones instead. However, if you are well-versed in navigating the BIOS, then follow the steps below.
Note: If updating the BIOS didn’t help, you might want to consider resetting it instead.

Error CausesCode 33 is a typical Device Manager error. This error code occurs when Windows is unable to start a device that you are trying to use on your PC. The error code 33 is usually displayed in the following format:
“Windows cannot determine which resources are required for this device. Code 33”
Error CausesError code 33 may be triggered due to two reasons. One reason can be the translator's failure to find the correct resource for the device driver.
And since this error code is associated with the Device Manager, another reason can be an outdated or corrupted device driver. In most cases, the underlying problem for Device Manager error code is outdated/corrupted drivers.
The good news is that Device Manager error code 33 is not detrimental. However, if the error is not resolved timely, it can lower the functionality and the performance of your PC. You may not be able to use the hardware device.
To resolve code 33, you don’t need to be technically sound or hire a professional computer programmer. Just like any other Device Manager error code, code 33 is also easy to repair.
To help you fix this issue on your system, below are some of the best, easy, and effective DIY solutions.
Properly configure the problematic hardware device to fix error code 33. It is important to understand that when you install a device that is not plug-and-play, the resource settings are not configured automatically.
This means for such devices you will have to perform device configuration manually.
For device configuration, here’s what you should do:
Code 33 can also be generated due to driver problems. In such a scenario, it is recommended to update the outdated or corrupted drivers.
Identifying all problematic drivers and updating them individually can be frustrating and time-consuming. Therefore to save time and avoid the hassle involved in updating drivers manually, it is advisable to download DriverFIX.
DriverFIX is a next-generation and user-friendly program compatible with all Windows versions.
This software is exclusively designed to repair and resolve device driver-related problems and error codes.
Once installed, its intelligent and intuitive programming system detects all outdated, corrupted, and misconfigured device drivers on your PC. It automatically updates all the problematic drivers in a few seconds. It makes sure that the driver versions are the latest and compatible with your operating system.
Furthermore, it also ensures that drivers are continuously updated whenever new versions are available. So, you don’t have to worry about keeping device drivers up to date.
Click here to download DriverFIX to resolve Device Manager error code 33 today!
“Windows could not configure one or more system components. To install Windows restart the computer with error code 0xc1900101-0x30018.”When you check on the Windows 10 rollback log, you will see a part with the “iisetup.exe” that’s related to the abort. Usually, the upgrade process completes over 50% and gets stuck and then rolls back later on and generates the error logs. This kind of error, in most cases, appears during the upgrade of Windows 10 and is related with the Internet Information Services or IIS in Windows 10. For some unknown reason, it restricts the installation or the upgrade which causes the error to appear. To fix the “Windows could not configure one or more system components” error, you can try to remove the IIS from the Windows Features or rename the “inetsrv” folder. You could also move all the folders related to IIS to another drive. For more details, refer to the options provided below.
How this is the case we have decided to put a little tutorial on how to accomplish this very task and run file explorer with administrator privileges.
Windows 10X is a new version of Windows that has been built from the ground up for new PCs and will begin shipping on hardware in 2021. It's built on top of a new modern version of Windows called 'Windows Core OS' that guts legacy components and features in favor of contemporary user experiences and enhanced security. This means everything from the Windows Shell to the underlying OS has been rebuilt with modern technologies.
As a result, Windows 10X does not support legacy Win32 applications at launch. Windows 10X PCs in 2021 will be able to run Microsoft Edge, UWP, and web apps. Legacy Win32 application support will arrive at a later date, however. When it does, Win32 applications will run in a secure container by default, meaning those legacy applications cannot affect system performance and battery life when closed. Windows 10X is a much more secure and stable OS as a result of this, as there's no opportunity for legacy apps to cause bitrot.
Windows 10X features a new shell of the user interface that has been built with modern technologies. It's an adaptive user experience that can adjust depending on the "posture" of your device. For example, with a foldable PC, the user might want to use it in several different ways; as a laptop, or tablet, or in tent mode for movies. Because of this, the user interface must adapt to provide the best experience no matter which way your device is being used. This also means that legacy shell elements, such as the Control Panel, File Explorer, and error dialogs and icons are gone on Windows 10X. As Microsoft has rebuilt the entire shell, it doesn't include any of the legacy things that make Windows 10 so inconsistent when it comes to UI. The Windows Shell on Windows 10X should be much more consistent. At launch, Windows 10X will only be available on traditional clamshell PCs aimed primarily at the education and enterprise markets. The platform will eventually ship on the new devices from factors such as foldable PCs, but that won't be happening in 2021.Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
Error CausesIn attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Error Causes
So, next time when you or your friends encounter this problem, try these quick fixes to repair the error without any hassle.