Share via

False WindowBlinds detection blocking Fall Creators Update

Anonymous
2017-10-19T05:07:15+00:00

When attempting to install the latest Feature update to Windows 10 version 1709 on my Windows Pro desktop halts with a dialog asking for WindowBlinds to be uninstalled as it is not compatible. The problem is that WindowBlinds has never been installed. I can't remove an app that is not there.

Is there a way to override the WindowBlinds detection and proceed with the upgrade? Alternatively, does anyone know what the WindowBlinds detection is looking for so that I could manually remove what it is falsely detecting?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

27 answers

Sort by: Most helpful
  1. Anonymous
    2017-10-28T12:47:20+00:00

    I got it :-)

    i did follow steps:

    browse to "C:$WINDOWS.~BT\Sources\Panther" (you can copy past it) search for "Compat*.xml" sort by date and open the file in the notepad you will see in any line the file that block the update 

    </DriverPackages><Programs><Program Name="WindowBlinds" Id="" IconId="windowblinds600_|870b02a0dcd67421"><CompatibilityInfo BlockingType="Hard" StatusDetail="UpgradeBlock"/><Action Name="ManualUninstall" DisplayStyle="Text" ResolveState="NotRun"/></Program></Programs></CompatReport>

    i use Everything (http://www.voidtools.com/) to find this file, it was a old installer on my d:\ drive (not used since 2007) after i delete this file, i can install the update

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2017-11-20T22:31:19+00:00

    Using SliderOverride's approach fixed this problem on my system and allowed me to install the Fall Update with zero issues and retain all my already installed programs.  It saved me many hours from having to reinstall and reconfigure - thank you SO!

    SO wrote: i use Everything (http://www.voidtools.com/) to find this file, it was a old installer on my d:\ drive (not used since 2007) after i delete this file, i can install the update

    My approach was somewhat different.  I had never INSTALLED *any* Stardock product in Windows 10 *but* I still had several instances of 'WindowBlinds' on archive drives in my system and sure enough SO was correct, *simply having the Windowblinds executable file* in a folder on an archive drive *prevented* the Fall Update to install.  I kept getting the message that Windowblinds was not compatible with the update, but had *never* installed it under Windows 10, and that is even with a fresh Windows 10 install on this system. 

    Here is what I did:

    #1:  Downloaded and installed WindowBlinds 10.65 from the Stardock website (BTW, it works great with Windows 10).

    #2:  UNINSTALLED Windowblinds using the 'remove programs' in the Win 10 control panel.

    #3:  Using the info SO provided, I downloaded and installed "Everything," ran it, and removed (deleted) *ALL INSTANCES* of Windowblinds on all hard drives. "Everything" is public domain and free to download and what I see it has no spam hooks whatsoever.  (http://www.voidtools.com).

    Once all instances of 'Windowblinds' references that 'Everything" found (it searches all your hard drives) were removed, I ran the Microsoft "MediaCreationTool.exe" from the Microsoft update website (link found in this thread) and the Fall update installed flawlessly.

    Thanks again to SO (and Microsoft for the great features in the Fall Update).

    6 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2017-11-04T15:30:24+00:00

    It's silly problem (bug) where if Windowsblinds6 installation file is anywhere on your PC (Doesn't need to be installed or ever installed or any traces) it will stop the install process dead.

    I had an old version (never installed) sitting on my PC in a Stardock repository. Deleted it and things worked great.

    Silly Microsoft issue - shouldn't look at the entire disk area.

    Jim

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-10-27T10:07:30+00:00

    I have. I'm developer so I have a lot of MS stuff looking like system updates, SDKs, VS addons, etc. Bot nothing 3rd party that I can't recognize.

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-10-20T04:08:08+00:00

    Thanks lacrumb for responding. Your suggestion doesn't help though. WindowBlinds is not a form of malware. It is a Windows desktop theme and UI app from Stardock. Malwarebytes or Windows Defender would not see it as a threat that needed quarantine.

    I scanned the Windows Registry and Installer database for any WindowBlinds entries and there were none. I suspect that a different app installs a file with a similar name somewhere that triggers a false positive for WindowBlinds. I did try and install the latest version of WindowBlinds and then uninstalled it. That had no change in the Fall Creators Update install blocking behavior.

    2 people found this answer helpful.
    0 comments No comments