loads classic at startup

when i reboot my computer the theme changes back to windows xp classic anyone know why
cheers
6,605 views 27 replies
Reply #1 Top
I had the same problem, so I applied the uxtheme patch to Windows XP. This allows the OS to use unsigned 3rd Party themes. Given how many people have this problem, perhaps this is more to this answer, including a possible software bug?
Reply #2 Top
jimmi1, I assume you are having this problem with Windowblinds? If so, applying the uxtheme patch to Windows XP is not the answer. Try uninstalling Windowblinds then reboot and reinstall Windowblinds via Stardock Central. If the problem still persists copy and paste your system info from Windowblinds and we'll take a look at it
Reply #3 Top

If you are at the end of a 30 day trial, then WindowBlinds will not function. That it what it is designed to do - 30 days means 30 days... You will have to uninstal it. The either not use it, or purchase the full version.

Try selecting an XP type theme from desktop properties. Patching uxtheme.dll is not recommended.

Reply #4 Top

Patching uxtheme.dll is not recommended.

End of quote


Why is this not recommended? It's the only way I could get Windows to allow me to use modified themes.
Reply #5 Top
Interesting, IceIsles joined us yesterday  ;) 
Reply #6 Top
Interesting, IceIsles joined us yesterday   
End of quote


Indeed - I am oblivious, incoherent, and borderline incompetent.  :D 
Reply #7 Top
Is it not better to teach then ridicule as it is better to learn and gain wisdom?   :SURPRISED: 

Damn that's good, got to write that one down. :LOL:  :LOL:  :LOL: 
Reply #8 Top

It is not recommended because you are both altering a system file and breaking the EULA.

Altering system files can lead to unpredictable results. If you want to do it, fine, just don't recommend it to anyone else.

Reply #9 Top

It is not recommended because you are both altering a system file and breaking the EULA.


Altering system files can lead to unpredictable results. If you want to do it, fine, just don't recommend it to anyone else.

End of quote


I gotcha. With me, it was a matter of necessity. I wanted to use WB6, and this was the only way to go about it. I generally agree about not altering system files, although MS has gotten a lot better about locking users out of critical services, etc.
Reply #10 Top
IceIsles, I'm intrigued. You wanted to use Windowblinds so you used the uxtheme patch  :NOTSURE: How did you do that?
Reply #11 Top
IceIsles, I'm intrigued. You wanted to use Windowblinds so you used the uxtheme patch   How did you do that?
End of quote


For some reason, Windows wouldn't let me select a "modified theme" when I installed WB6. Subsequently, although WB6 was installed, everything was permanently stuck in "Classic" mode. I honestly don't know much about the uxtheme patch, but it did the trick for me. I figured I could always restore a backup if it torched my OS.  :D 
Reply #12 Top
hi thanks for the replys everyone i had a problem when i was installing it kept telling me to reboot and i had to select use additional processes option do you think that could be the problem or something to do with it
Reply #13 Top
i am using windows blinds 5.1 xp pro sp2 x64 i applied the uxtheme patch but when i rebooted it told me that it could not find uxtheme.dll so i had to resort back to the other one
Reply #14 Top
i am using windows blinds 5.1 xp pro sp2 x64 i applied the uxtheme patch
End of quote


the patch is for StyleXP not WB

open WB config and click the system info and post the info that shows up
Reply #15 Top
WindowBlinds 5.1 System Information Report:

STATUS : WB+ SRV+ HLP+ UI+ TRAY+

WindowBlinds is installed correctly on this PC.

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

(Plug and Play Monitor) 1 is Radeon X300/X550/X1050 Series

Wblind.dll 2006/10/27 17:20:20
Wblind64.dll 2006/10/09 12:51:37
Wbsrv.dll 2006/10/09 13:25:43
Wbconfig.exe 2006/10/28 18:13:27
Wbload.exe 2005/12/21 01:04:47
Wbhelp.dll 2004/09/18 16:37:07
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/28 19:27:49
Reply #16 Top
jimmi1: where did you get your 5.1 from?


Wblind.dll 2006/10/27 17:20:20 = No match what I show for Trial/Standalone/SDC
Wblind64.dll 2006/10/09 12:51:37 = Match what I show for SDC
Wbsrv.dll 2006/10/09 13:25:43 = No match what I show for Trial/Standalone/SDC
Wbconfig.exe 2006/10/28 18:13:27 = No match what I show for Trial/Standalone/SDC
Wbload.exe 2005/12/21 01:04:47 = Match what I show for Trial/Standalone
Wbhelp.dll 2004/09/18 16:37:07 = Match all
Wbui.dll 2005/12/06 22:29:06 = Match what I show for SDC
Tray.dll 2006/04/28 19:27:49 = Match what I show for Trial/Standalone


Reply #17 Top
How do you find the "correct" dates? Is it open to the public, or for SD and WB staff/mods only?
Reply #18 Top
How do you find the "correct" dates?
End of quote


find them where?

normally, you just open WB, click system info and voila.. there they be
Reply #19 Top
Bichur I think what Pugboy is asking how do you come up with current dates for all versions (trial, standalone, SDC).  :NOTSURE: 
Reply #20 Top
Yup. I don't suppose us average joes can get a hold of those... Would be handy info...
Reply #21 Top

Bichur I think what Pugboy is asking how do you come up with current dates for all versions (trial, standalone, SDC).   
End of quote


For the SDC
every time I upgrade...
I open WB, click system info and voila... there it be

The Trial/Standalone are basically the same, just one has activation
every once in a while some post their standalone info for reference

then i copy to a text doc for later reference

Reply #22 Top
Yup. I don't suppose us average joes can get a hold of those... Would be handy info...
End of quote


you'll find valid and cracked posted throughout the forum
Reply #23 Top
most of the times, with the dates it's not too hard to figure out there's incorrect files involved

for example:

a 5 version came out on 11/28/2005

LEGIT

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/11/28 15:52:00
Wbconfig.exe 2005/11/28 16:19:00
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26

the newest file date is 11/28

then you people looking for help posting:

Cracked

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/06 21:16:30
Wbconfig.exe 2005/12/03 03:03:36

Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26


Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/03 04:03:40
Wbconfig.exe 2005/12/03 04:03:36

Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26

Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/12/07 02:16:30
Wbconfig.exe 2005/12/03 08:03:36

Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 15:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26
Reply #24 Top
Uh oh... Dates are invalid=Not good
Reply #25 Top

Uh oh... Dates are invalid=Not good
End of quote


nope