How do I fix error 0xc1900209

This maybe an issue with a system file being corrupt.

You can try a couple things.

Right click your start button and select Command prompt (Admin) to bring up elevated Command prompt.

In Command prompt type sfc /scannow and press enter.

Restart the computer.

If that doesn't work then try this,

Right click your start button and select Command prompt (Admin) to bring up elevated Command prompt.

In the Administrator: Command Prompt window, type the following commands.

Press Enter key after each command:

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

Important: When you run this command, DISM uses Windows Update to provide the files that are required to fix corruptions.

To close the Administrator: Command prompt window, type Exit, and then press Enter.

Restart your computer.

This is an extreme attempt by Microsoft to force people to upgrade their systems whether we want to or not. This is very similar to what they did to one of my Dell laptops when they forced a Windows upgrade to Window 10 from Windows 7 even though the Windows 7 machine was not certified to be upgraded. Needless to say the upgrade failed and made a very fancy paper weight out of an expensive i7 Dell laptop. When I complained about the issue to Microsoft I was ignored. Cost me $289 to replace the motherboard and then I needed to block all future upgrades to that machine.

Microsoft is only interested in being the biggest PC operating system and not in what is best for the consumer. My current machine is a new Dell XPS i7 desktop Windows 10 Pro with all the bells and whistles and they are trying to force the machine to update to version 1709. I get an error of 0xC1900209 which goes further to identify the offending software as my Symantec Endpoint Anti-Virus. The solution is to uninstall the anti-virus software for the machine to update. With a considerable amount of experience with Microsoft and their approach to things, I don't consider the uninstalling my anti-virus an option. Stop and think if I uninstall and allow Microsoft to force an update that is not compatible with my anti-virus, then when I want to reinstall my protection it won't work. That leads to further problems of finding a software package that will work. Again stop and think, if Microsoft's biggest and best Operating System can't be or won't be compatible with one of the best and largest anti-virus companies, then what makes me think I will be able to fix a machine that was force to update to something that has so many problems.

Has anyone actually read the recommendation and work-arounds to upgrade to the Creators version 1709 of Windows 10? Last time I thought about trying it, there were 12 different steps or procedures you had to do before the upgrade "Might" install. It wasn't an option for me to spend hours trying to install something that might or might not work and could cause extensive damage to my expensive new machine. Now Microsoft has devised a plan to install Windows Update Assistant and a series of nags and interruption to force me to install something I don't want or might not even run on my new machine.

I'm so feed up with the high and mighty attitude of Microsoft and the fact that they will make us upgrade or update or they will stop the support for a version that we bought to initially run our machine. When will it all end? I know it will end when we all move to Apple's IOS. Funny how all their update work flawlessly.

That error concerns incompatible software which is preventing the upgrade, you’d have to discover the software - possibly anti virus software - & uninstall it.

Check these sites for possible solutions - remember not to click on any auto fix software which might be on these sites.

https://windowsreport.com/error-code-0xc1900209...

https://appuals.com/windows-10-update-error-0xc...

Hi there? If you still suffer from this error code and after a lot of research I found the problem and the solution... for me at least. Let me deal with two different situations.

1. If you run Windows 7 or earlier then you probably also run the Intel 'booster' package. This makes Win7, Vista and others start faster.... but it also BUILDS A RAM DRIVE!! If you open Device Manager at look at your hard drive details you should see something called IDM-0 AS WELL AS your real drive. You might just be able to delete this and then run the Windows updates but a reboot (needed later) will bring it back! So I suggest you UNinstall the Intel Booster app package AND delete the RAM drive!! Restart the PC and away you go!! If you put it back I suspect you will get the problem again!
2. If you are running Win10 then you will also see the IDM-0 RAM drive so do the same as above. But you need not have installed it and certainly do not repeat your error. Win10 does NOT need the Intel 'go-faster strip'!!

If you are unsure of what you have then check for the IDM-0 drive in Device Manager. If it is there then dump it... if not - and you still have the error - then look for something similar!!

It definitely seems to be caused by an unwanted or inadvertent RAM drive!!

Good luck

Tony

Believe it or not I finally got the fall creators edition of Windows 10 to update on both my machines (Dell i7 Desktop and Dell i7 Laptop).

Here was my experience. The update told me Endpoint from Symantec (Anti Virus) was the issue and to uninstall it. I got brave enough to do that with back ups and system disks standing by. Of course the uninstall didn't do enough for windows to install on the first attempt, so I used "Regedit" and searched for anything with the name Symantec. After almost an hour of edits, I could find nothing about Symantec in the Registry. After all that the windows update actually loaded. Of course it took most of the day to complete but it loaded. After the update seemed to be working I tried to reload Endpoint. That worked as well except that I used the package that had been loaded before and got an error saying Windows 10 does not support this 32 bit version of Symantec. I dug around and found my 64 bit version and guess what, it loaded and is working fine.

Moral to the story: Microsoft and Windows update should have told me about the 32 and 64 bit issue before I spent months worrying about how I was going to fix a stupid problem, I knew nothing about. Also as an extra note, the laptop loaded fine after a simple uninstall of Endpoint. Why the difference between the machines? Something only Microsoft knows and will never tell...