Skin need sto be reapplied when computer starts up

from Stardock Forums

Hey guys,

 

Whenever I start up my PC, my skin seems to have been loaded in Compatibility mode or something, and some of the elements are completely different than normal. If I just reapply the skin, it gets fixed, but it's a bit of a pain to do this every time. I've tried editing the skin to only have one style, but it still seems to find it's way back to this other look. I have Windows 7 and WB7, and I'm using a custom version of this skin: https://www.wincustomize.com/explore/windowblinds/7091/

 

Thanks!

windowblinds
11,524 views 14 replies
Reply #2 from WinCustomize Forums Top

I have the same issue, however, it doesn't happen every time.  I estimate about one in five start-ups I have to reapply the skin. When it's reapplied, it creates a small file named .WBO in the Doucuments/Stardock/WindowBlinds/WBO folder. Windowblinds service is running in the background.

Galactic Civilizations III
Reply #3 from WinCustomize Forums Top

Quoting MeSleeper, reply 2

.WBO
End of MeSleeper's quote

Never heard of this problem. I would suggest you check out this link. At the bottom it gives you more information about what to do.

http://en.filesupport.org/file-extension/wbo

Reply #4 from Stardock Forums Top

I have the same issue when i go to mylockscreen and i come back ton my session.

Reply #5 from Stardock Forums Top

I've had a look in my WBO folder and I can see there's 2 for my skin, one that's got the .WBO extension, and one that's got a .WBO7 extension.Would having the two of these be causing the behaviour I'm experiencing?

 

As someone mentioned this happens after logging in from the lock screen, I guess I should mention that this happens to me if I play some games (Such as Battlefield 4), which is what was leading me to thinking it's some sort of Windows Compatibility mode problem, although I could be way off mark there.

 

As for the WBO files, should I associate them with the WB7 exe?

Reply #6 from WinCustomize Forums Top

Quoting CSMoneybags, reply 5

As for the WBO files, should I associate them with the WB7 exe?
End of CSMoneybags's quote

From the link I provided it says to get rid of the wbo as it is causing all your problems. I don't know anymore about it but it sounds like you have malware or something and tells you to do scans with programs. I read several sites on this and it sounds like it could have even effected the registry. 

Reply #7 from WinCustomize Forums Top

Quoting DaveBax, reply 3


Quoting MeSleeper,
reply 2

.WBO



Never heard of this problem. I would suggest you check out this link. At the bottom it gives you more information about what to do.

http://en.filesupport.org/file-extension/wbo

End of DaveBax's quote

Whenever I have the start-up glitch, I just go to the folder and delete the 100 K .WBO file.  No big deal.  I suspect there is some conflict with WB during start-up. Maybe a conflict with the video driver?  NVidia drivers have been a bit quirky lately. Just wanted the OP know he's not the only one seeing this issue.  My instances are just a lot less often than his. 

Reply #8 from Stardock Forums Top

It's been almost 6 months now and I have still not solved this issue. Through experimentation, I think I've confirmed what MeSleeper suspected with the WBO files causing the issue - deleting it before shutting the computer down seems to prevent the problem from occurring again. I added a script to my start-up sequence to delete this file, but that does not seem to run in time to stop the problem happening. I also attempted to change the folder permissions to stop any writing to it, but apparently you can't control application permissions.

 

Does anyone know of a way to automatically empty this folder before the computer shuts down? Or even a way to just "fix" my WB install or theme so that the WBO file doesn't cause this problem?

Reply #9 from WinCustomize Forums Top

There is probably something wrong with your installation...
DID you contact support yet?

Best would be to contact the Stardock support to solve the issue.

Stardock IRC support chat 

or email support@stardock.com

Reply #10 from WinCustomize Forums Top

Silly question, but have you emailed support@stardock.com yet? If not you should do so and wait for a non-automated reply before responding again so you don't get put back in the queue. Might be a good idea to reference this thread in your initial email to them also, and post your ticket number here when you get the automated response.

 

Sorry benmanns, guess we were posting at the same time.  :)

Reply #11 from Stardock Forums Top

Hmm, it seems silly to me now that I havn't done that yet! I'll do so now.

 

I'm hesitant to re-install it, as this computer was built in January and everything installed from scratch - and I like to think I have the technical skills to install it properly haha! But, you never know...

 

I'll update when I hear back from Support. In the meantime, if anyone figures it out, feel free to let me know :p

Reply #12 from Stardock Forums Top

Support have replied and recommended I upgrade to WB8 as 7 is not supported anymore. Quick response, but not very helpful sadly!

Reply #13 from WinCustomize Forums Top

This happens to me only after using one application and that is when i play The Settlers II. As this game comes as a DOSbox wrapped program. (the only way it will run on a windows 7 64 bit system). After exiting the game my windows UI reverts back to the windows basic scheme and a box opens up telling me that The Desktop Windows Manager has stopped working. Reapplying the theme through WB Config sorts this out. It just may be that the two applications don't talk together correctly. I consider this such a minor issue that i have never mentioned it until now. If that's the most inconvenient thing that happens to me on any given day i consider myself blessed so i just put up with it and keep on rocking (in my case hobbling) but just sayin' :) 

Reply #14 from WinCustomize Forums Top

Interesting that it is possibly related to dosbox,

on my 64 bit  eralier 8 version i do too have the bug described.

Perhaps its fixed now, but i don t really care about it. ( its not like i turn on my win7 24 times a day or more).

 

regards bluedxca93