Installation Problem Windowblinds 5.51 Enhanced
from 
Stardock Forums
Stardock Forums
My problem is talked about (sort of) in a couple threads, but it's different enough I thought I would start a new thread. Hope that's alright 
I've been using Windowblinds 5.50 without incident. I updated to version 5.51 by uninstalling 5.50 and then installing 5.51. Uninstall/install went without incident. After the 5.51 installation, I removed the installation skins and added my preferred skins. I also re-set my wallpaper.
Everything worked fine until I re-booted. Windowsblinds 5.51 would not start (most of the time) on boot up. Windows defaulted to classic mode. Windowblinds would run if it was started manually. I say would not run "most of the time" because Windowblinds curiously enough did occasionally start automatically on re-boot. My OS in XP with all security patches up-to-date. All firewall and anti-virus programs were unloaded before the uninstall and install processes were carried out.
Not knowing what to do, I uninstalled version 5.51 and re-installed version 5.50. The re-installed 5.50 version now behaved exactly the same as 5.51. Windowblinds required a manual start after re-boot.
I re-imaged my hard drive back to before the installation. Thinking something might have gone poorly during the uninstall/install processes, I tried everything again. I used a freshly downloaded 5.51 set-up file just in case the original download might have been corrupt. This second attempt yielded the same frustrating results.
After the second attempt, I tried disabling as many start-up programs as possible and rebooted. I thought that perhaps Windowblinds might be running into a conflict during start-up with something else. Nothing helped. One thing I wished I had tried was to install version 5.51 directly over 5.50.
I'm back now to the original 5.50 installation. I've tabled 5.51 until I know what's going on. This is the first time a Windowblinds installation hasn't gone perfectly. I suspect it's a complicated conflict with something on my system. I doubt it's a huge problem or the forum would be going nuts discussing it.
Any one have any thoughts on what might be causing this problem? Thanks
I've been using Windowblinds 5.50 without incident. I updated to version 5.51 by uninstalling 5.50 and then installing 5.51. Uninstall/install went without incident. After the 5.51 installation, I removed the installation skins and added my preferred skins. I also re-set my wallpaper.
Everything worked fine until I re-booted. Windowsblinds 5.51 would not start (most of the time) on boot up. Windows defaulted to classic mode. Windowblinds would run if it was started manually. I say would not run "most of the time" because Windowblinds curiously enough did occasionally start automatically on re-boot. My OS in XP with all security patches up-to-date. All firewall and anti-virus programs were unloaded before the uninstall and install processes were carried out.
Not knowing what to do, I uninstalled version 5.51 and re-installed version 5.50. The re-installed 5.50 version now behaved exactly the same as 5.51. Windowblinds required a manual start after re-boot.
I re-imaged my hard drive back to before the installation. Thinking something might have gone poorly during the uninstall/install processes, I tried everything again. I used a freshly downloaded 5.51 set-up file just in case the original download might have been corrupt. This second attempt yielded the same frustrating results.
After the second attempt, I tried disabling as many start-up programs as possible and rebooted. I thought that perhaps Windowblinds might be running into a conflict during start-up with something else. Nothing helped. One thing I wished I had tried was to install version 5.51 directly over 5.50.
I'm back now to the original 5.50 installation. I've tabled 5.51 until I know what's going on. This is the first time a Windowblinds installation hasn't gone perfectly. I suspect it's a complicated conflict with something on my system. I doubt it's a huge problem or the forum would be going nuts discussing it.
Any one have any thoughts on what might be causing this problem? Thanks
WinCustomize Forums
