- 0 – Incognito mode is enabled by default
- 1 – Incognito mode is disabled
- 2 – Chrome is forced to always open in Incognito mode
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:
In some cases, you might be opened to other error messages when attempting to update to Windows 10, including error code 8007002c.
In fixing issues related to error codes, it is best to employ manual repair methods. Using these methods helps users pinpoint the root causes of the issue and apply solutions permanently to fix the issues.
While most manual repair methods can be done by every Windows user, even those without technical abilities, there are certain cases where help from a Windows professional is needed. If you’re not up to facing risks in implementing manual methods yourself, consider getting help from a professional Windows technician or you can use a powerful automated tool.
In fixing Error Code 0xC1900101-0x30018, you can repeat the same steps used for 0xc000021a (Method One) or you can try doing the following:
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
Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!

In the dialog, type in netplwiz and press ENTER.
You will find yourself in the User Accounts window, inside deselect Users must enter a user name and password to use this computer. Press OK
Sign in the window will pop up where you will have to type in your password and confirm it in order to start the feature.
After typing in your password and confirming it, press OK. That's it, next time you wake your computer from hibernation or turn it ON, you will automatically be greeted with a desktop instead of a Windows login screen.
Good thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this.
Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:
As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)… Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:
That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another device user might be using at any given point? We’re definitely not going to let a website know all the devices a given user might be using at any given point. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.
Run the Windows Memory Diagnostic tool
Error CausesCHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.