FIXED: Creators Update Not Installing - Incompatible App Was the Cause

Ketchup

Elite Member
Sep 1, 2002
14,546
238
106
FIXED: See post #9.

This is on the rig in my sig, currently running Windows 10 build 14393.969. It installed fine on one other machine I tried - a laptop.

I followed the link in the availability the message from Windows Update. On the desktop, the app just kept restarting. Goes all the way to 100% with the download, runs to 100% again and I can tell it's running the processor and drive, then just goes back to the beginning. No errors. Reboot, same thing. No errors on the screen.

So this gets old real fast. Went to the GetCurrent\Logs directory and found a log file - downlevel_(date).txt. Here is where I finally get to the error:

2017-04-11 20:53:17.686, Error [RunSetupForWin7LaterDelegator::ExecuteAction] Setup execution result failed! (HRESULT)dwExitCode = 0xc1900208

So, 0xc1900208 is the code one gets when incompatible software is found. OK .

Here is my question - is there any way to know what this software might be? In the AV department I am down to Windows Defender. No games from the store. Some older games that do run on the current build - do I need to start going through those? What I (we) really need is a Microsoft app that will do this for me (us).

Any advice appreciated.
 
Last edited:

Ketchup

Elite Member
Sep 1, 2002
14,546
238
106
I ran the troubleshooter. It suggested removing files and starting over (which I had already tried), but I let it do its thing. Ran through the process, same results. And error line in the log is the same. Thanks for the suggestion.
 
Last edited:

deustroop

Golden Member
Dec 12, 2010
1,916
354
136
Assuming the two machines have the same OS, how about looking for the outlier apps, the apps not on the laptop, and removing them from the desktop?
Serious surgery I know.
 

Ketchup

Elite Member
Sep 1, 2002
14,546
238
106
Yeah, if it comes down to that - there are a lot of them - the desktop is the main family rig. The laptop is just for Internet and Email. If nothing else, I will just start from the oldest programs and work my way up.

I just don't understand why Windows can detect a program that will supposedly cause a problem, but can't tell you what it is? If that is even what the issue means in this scenario.
 

deustroop

Golden Member
Dec 12, 2010
1,916
354
136
You don't have any "untoword" apps do you ?

I found a case where Windows 10 would not install on a machine that ran a file called nasca.drm.

(lol
that's just asking for trouble.)
 
Last edited:

RLGL

Platinum Member
Jan 8, 2013
2,089
305
126
3rd party Av programs have been problematic for the recent builds. If you are using AV and firewall other than Windows Defender, remove them let defender start and try it again.
 

Puffnstuff

Lifer
Mar 9, 2005
16,054
4,808
136
My desktop is loaded down with software including classic shell and 8gadgetpack (which gave the original 10 upgrade installer a fit and wrecked the install) and I didn't have a problem updating. Have you considered trying it outside of WU? The media installation tool has helped me in the past when a WU issue prevented an install.
https://www.microsoft.com/en-au/software-download/windows10
 
Last edited:
  • Like
Reactions: PliotronX

Ketchup

Elite Member
Sep 1, 2002
14,546
238
106
FIXED... Glyph was causing Windows to stop the upgrade.

I let Windows do its patch yesterday, then I attempted the Creators install again. It failed again, but this time showed a notification about it, and took me to Windows update to fix. Then Windows Update tried the upgrade, failed, and finally showed me the program causing the problem (Glyph, for Trove, a game our kids play). After an uninstall, Creators installed fine.

Thanks for your input.

I am still not sure:
a) why it couldn't just say "this program is not going to work after you upgrade," as I have seen previous versions, and move on.
b) why the log file wouldn't point to the program/file that was causing the error in the first place.
 
Last edited:

Puffnstuff

Lifer
Mar 9, 2005
16,054
4,808
136
Since MS was nice enough to post the 1703 ISO's I went ahead and downloaded them just in case I need to do a clean install. I suppose that I need to breakdown and make a bootable thumb drive with it too.