WindowBlinds additional Google Chrome.zip for Windows 10 will not install

I just reinstalled Windows 10 on a new hard drive, and am attempting to reinstall my Object Desktop apps starting with WindowBlinds. I downloaded the most recent one available. Upon installing, 2 issues arose:

(1) The taskbar does not skin. I  am using the same WB as before and did not have this problem with my previous installation of WB in Win10 on the old hard drive. Everything worked perfectly before.

(2) I followed the link in the WindowBlinds setup screen "Learn more about skinning Google Chrome" which advises that Chrome does not skin in Windows 10 (which is weird, because like I said before, I never had these issues before) and I downloaded the Google Chrome.zip file that contains a single .lnk file. The information stated "Also note that this link only works if you installed Chrome in its default location."

When I try to run the file in Google Chrome.zip I get an error saying 

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"

The specified path does not exist.

Check the path, and then try again.

The problem is this: When I installed Chrome and allowed it to install to its default location, it installed in C:\Program Files NOT in C:\Program Files (x86)

So I uninstalled Chrome, thinking I would reinstall it and specify the (x86) folder as the installation location this time. However, when I ran the install, it did not give the option of installing it to the location of my choice. It automatically installs it in the C:\Program Files folder without allowing user input.

The Stardock file will only work if it is installed in the (x86) folder. Since Chrome will not give the option to install in the (x86) folder, how does one get this file to work?

 

13,275 views 9 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Need to know more on your system.

  1. Windows version, please use Winver.exe for full version numbers.
  2. Is this a new system? Hardware spec? CPU? Intel, AMD or ARM(Snapdragon)?
  3. Have you tried reboot, uninstall, reboot, install and reboot again?

Thanks.
Basj,
Stardock Community Assistant.

Reply #2 Top

Windows 10 Home Version 1909 (OS Build 18363.1082)

CPU: CPU: AMD Phenom II X4 965 with 16GB installed memory

New hard drive for the OS, not new system entirely. I have built my own from scratch for 25 years so that I can put in what I want and update individual components when needed instead of having to go along with proprietary packaged systems. (And thus my need to completely change the GUI immediately after installing an OS. In the beginning, it was collecting icons for Windows 3.1 and learning to change the bootup screens. My Stardock addiction began with my April 1999 purchase of WindowBlinds ver. 1.0 and took off from there.) 

Old 250GB C: drive was starting to fail, so reinstalled Windows 10 on a new 2 TB Western Digital Barrauda HD, hence the reinstall of all of my Stardock GUI-tweaking apps. For Stardock's Google Chrome.zip file "reboot, uninstall, reboot, install and reboot again" does not apply. As I described, while Stardock says it requires Chrome be installed in its default directory, the actual default directory it installs to is C:\Program Files, not C:\Program Files (x86) like Stardock thinks it is, and the Chrome installation process does not allow it to be changed.

Many thanks for your help, basj... I've been privileged to acquire lots of your work over the years here too!

Reply #3 Top

Quoting BBartCP, reply 2

(1) The taskbar does not skin. I am using the same WB as before and did not have this problem with my previous installation of WB in Win10 on the old hard drive. Everything worked perfectly before.
End of BBartCP's quote

Would like to try to solve this one first. Few questions.

  1. Is the issue happened on all themes/styles/skins? Or only specific skins?
  2. Have you tried the purge and reinstall steps :  Please try purge and reinstall steps as mentioned here: https://forums.wincustomize.com/486023/windowblinds-support-faq#reinstalling Just make sure to redownload the latest version from your account. Reboot after the purged. Reinstall, and Reboot again after the installation. Retest it. Report back here.

Thank you,

Basj,
Stardock Community Assistant

Reply #4 Top

Question: Why are you using Win version 1909 and not 2004?

Reply #5 Top

"Also note that this link only works if you installed Chrome in its default location."

The problem is this: When I installed Chrome and allowed it to install to its default location, it installed in C:\Program Files NOT in C:\Program Files (x86)
End of quote

The convention in Windows is for 32 bit programs to install in "C:\Program Files (x86)" and 64 bit programs to install in "C:\Program Files".  Since Chrome is now a 64 bit application it no longer installs to "C:\Program Files (x86).  The LNK file needs to point to the correct path.

Reply #6 Top

Quoting Victechnical, reply 5


Quoting ,
"Also note that this link only works if you installed Chrome in its default location."

The problem is this: When I installed Chrome and allowed it to install to its default location, it installed in C:\Program Files NOT in C:\Program Files (x86)


The convention in Windows is for 32 bit programs to install in "C:\Program Files (x86)" and 64 bit programs to install in "C:\Program Files".  Since Chrome is now a 64 bit application it no longer installs to "C:\Program Files (x86).  The LNK file needs to point to the correct path.

End of Victechnical's quote

That is odd Victechnical, I am running Google Chrome Version 86.0.4240.75 (Official Build) (64-bit), and it is installed to C:\Program Files (x86) . Might have been that I was using the 32-bit version and it upgraded itself to 64-bit though.

Reply #7 Top

Ah-HAH!!! I did not know this, but it completely explains the issue I'm having. I guess there's nothing to do now but wait for a Windows 10  64-bit version to be issued with an updated .lnk file (hint).  I have added a copy of this thread to the zip file for future reference. Thank you, LightStar! :sun:  

Reply #8 Top

That's what installed from my newly-purchased-from-Microsoft full retail box and System was telling me it was up to date (green check mark and all). I had to do a manual check of Windows Update after reading your post to discover there was an update to 2004 mentioned completely separately. :omg: I clicked on that, installed it and am now at Version 2004 Build 19041.508. I appreciate the heads-up!! |-)  

Reply #9 Top

Quoting LightStar, reply 6


 

 

That is odd Victechnical, I am running Google Chrome Version 86.0.4240.75 (Official Build) (64-bit), and it is installed to C:\Program Files (x86) . Might have been that I was using the 32-bit version and it upgraded itself to 64-bit though.

End of LightStar's quote

 

According to this page that's exactly right Lightstar.  If running 32 bit and then upgrading to 64 bit it stays in the x86 folder.  64 bit Chrome has to be uninstalled and then upon reinstall it will be put in "C:\program files"...

https://www.ghacks.net/2020/06/11/google-chrome-is-soon-going-to-be-installed-in-a-different-directory-on-windows/

 

https://bit-tech.net/news/tech/software/google-chrome-64-bit-upgrade/1/#:~:text='In%20order%20to%20improve%20stability,staff%20in%20a%20blog%20post.