How can you be sure it was not some other hack you had inflict on your poor system that we are not aware of? Altering the operating system is just asking for compatiblity problems.

Don't belittle me. The problem is not my computing methods. WindowBlinds WORKS on my system, no matter how hacked it may be. The problem is Impulse, a proprietary software installation platform designed to battle the foe known as PIRACY. One look at these forums shows just how "well" Impulse works. I'll bet money that I'm not the only one here who wishes Impulse had never been implemented...

No, respectfully I am not misreading your post.

I said you clearly NOW have managed to get an acceptable/workable sequence of install....one that THIS TIME did not hose your system and prevent a legitimate software install from functioning.

Yes, on these forums you will see literally DOZENS of posts relating to Instal problems with Impulse, just as with ANY software's Forums.  The reality, however is the VAST MAJORITY do NOT have issues at all.  Stardock has 4.4 million members registered most of whom will have Impulse installed [I don't know offhand the exact number].

Even a 'failure' rate [of painless installs] of say, 400 people will count as 0.01% of the user base.

People who alter system files prior/during/after a program install can look forward to/enjoy the experience of a failed program install which is just one of many reasons why MS has such things as protected OS files and UAC, etc.

The patched uxtheme.dll 'community' really needs a "do so at your own risk" warning, as I'm pretty sure their 'support' is non-existent.

Impulse is not "crap software", it actually works extremely well..... hence its commercial viability.

The same cannot be said for whatever recent permutation of the system hack is in current favour....;)

As someone who does some programming I would say given how hard it is to get a program to work fairly consitantly on unmoddified systems that people who do alter the OS should considers themselves blessed if even 50% of programs that interact with the moddified components work as intended.

No.

I've tried every step of the way to help. Now I say "no". Impulse is not the problem. uxthemes.dll is the problem.

Why?

Because you want WB7 to work on your system and Impulse will not do it's update and install function with the hacked system file present.

As I said before. Get rid of it, and do a good sweep of your system and storage (all devices) for it.

Then do chkdsk /f /r  to repair/fix what can be and note what can't be. If you ask for help, you should at least do what's asked of you or state why you won't.

Say Doc,

 Don't laugh at my ignorance, but I'm just wondered:  What is this "Hack"/patch thing you all are talking about?  I do want to avoid such things ones once I start using my StarDock apps.

Also in garbanz0's issue, he stated : "... and I'm told "You must allow Impulse to run as Administrator to continue.""

Why not make a Shortcut for the Impulse (or use one it comes with) and hit the "Run as Administrator" check mark (on whatever tab that is on).  I had to do this for a couple of apps when I first installed Windows 7 Pro x64.  Then I just found a utility type of thing that makes the user a SUPER Admin.  After all the confusion and mayhem caused by the dual token stuff MS introduced in the OS, it's not any wonder such crazy issue still abound.

I have been away from my career for some time, so I may be completely out in left field.  I do remember though, how many times I hit myself on the head when I refused to except that particular solution could NOT be "that simple". 

I 'll keep reading this tread, hopefully there is an answer out there for garbanz0.

Howdy BarJabba! Thanks for your suggestions and for your sympathy

The patch in question modifies some Windows files to allow users to install visual styles that have not been digitally signed by Microsoft. Despite all the loud voices in this thread suggesting otherwise, it's really quite innocuous. In fact, I have yet to see any evidence suggesting that my patched theme files are the source of the problem I'm having with Impulse, and I have already demonstrated that they have absolutely no bearing on the problems I had with WindowBlinds!

I have a suspicion that there is just a lot of animosity towards the patch (and its users) around these parts. After all, it lets users make their computer look nice without having to pay Stardock $20

Regarding the "administrator" issue, I wish things were so simple. I was in fact running Impulse as administrator... 

Simple search via Google....[" patched - uxtheme.dll - problems" ]

Posted 08 May 2008 - 10:30 AM

Hi, I tried installing the patch using method 2 "The replace installer" but after rebooting it came to the login screen and froze with the message " lsass.exe-Bad Image Dll C:\windows\system32\uxtheme.dll". The screen then goes to just the standard background and I cannot get to my desktop. I have tried logging in safemode and even restarting to the last saved restore point but neither trouble shoot has worked. I am unable to use my computer now and would really appreciate any help you guys could give. Thanks-Userlogin

This isn't about the legitimacy of the patch, or how well it works or doesn't work for individual users. I've been running it since XP and never had any problems with it. 

And it's not about "subverting" Stardock or its products. I have great respect for what you lot have done. I love WindowBlinds, and wish the talented creators of MS Visual Styles would migrate to WB, where their skills could be put to much better use.

No, this issue is about whether or not my patched theme files are directly responsible for Impulse refusing working properly on my system (While, curiously, WindowBlinds continues to get along with patched theme files just fine).

Until someone can demonstrate to me that my theme files are in fact the problem (because according to my tests, they are not), then my complaint is anything but unwarranted. 

Go on....give it a go.....Google the issues relating to the patching.  You may just find yours was the 'lucky experience'...;)

Am I doing it right?

http://lmgtfy.com/?q=stardock+impluse+problem 

Ok, all kidding aside (and please forgive my ineptitude), but how exactly will researching how other users improperly patch their theme files provide evidence that my patched theme files were causing Impulse to refuse to update? 

My theme files are patched, and both Impulse and WindowBlinds are running smoothly (after reinstalling Windows 7). What will it take for me to convince you lot that my patched theme files were not what was causing my problem??

How many goes did you have at getting it all to work?

You 'assume' the problem was/is with Impulse simply because you haven't observed any other conflict issue with your use of a patch.  Is it not equally valid that Impulse is simply the first program that brought the hack's failings to your attention?

I copy/paste an example of a person whose system was hosed due to his use of the patcher.  I saw no reference there to "oh....the patcher was running fine till I installed 'x'" ...it simply corrupted his sys files sufficiently to kill his system and he was stuck.

If you use a 'program' that is KNOWN to cause issues you cannot discount that truth simply because you got away with it OK - eventually.

I don't patch my uxtheme.dll .... I have no issues with installing Impulse or updating it....not on the 5 systems here ... ergo I can guarantee that NON-USE is not a problem.

Here's the trick....look at this closed test scenario..... 5 out of 6 systems Install/update Impulse without issue .  One requires a few goes at it from sys format and beyond.  5 do not use a patch. One does.

No, it's not a double-blind test methodology, nor even a reasonable statistical sample...but it's still indicative of a 'trend'....;)

Why are you so bent on blaming this on my theme patch when there is NO EVIDENCE that it is the source of this problem? Everybody here is just jumping to conclusions, it's completely absurd.

I'm sorry, but until a Stardock dev jumps in and says "yes, the Impulse installer/updater in fact checks your theme files, and it will refuse to operate properly if it finds that they have been tampered with", then nothing you say really has any merit.

In any situation you will be denied product support if you 'hack' or alter the system files under which the product is designed to install/function.

"Hi....I run a cracked copy of Windows 7 but it doesn't work right......"

Stardock [naturally] supports its products but if made aware of unsanctioned/unauthorised 'modifications' to the parent OS the first recommendation will be to revert to standard, whether the user 'believes' it is an issue or not...;)

The fact is you asked for help: You got help. You didn't do as advised. You were asked to run chkdsk /f /r that would have fixed/revealed system file and disk problems.

Instead, you reinstalled Windows and proceeded to hack it with that "patch". Don't complain that things don't work correctly or as they're designed to work on an intact/original OS.

What Jafo is saying to you is 100% correct. 

Ah, but things DO work properly with the patch installed, remember? Which leads me to believe that it was something else on my system causing the conflict. I wish I hadn't mentioned my theme files, I'll bet we would have found the real problem by now! I absolutely refuse to believe I'm the only WB user who also enjoys other methods of skinning...

(And I still don't see how checking for bad sectors on my storage drives is going to help solve a software issue on my system partition.)

Anyway, WB runs fine, and I can switch between WB themes and msstyles themes as I wish with no issues at all. That's what really matters.

OK...you're clearly attempting to be deliberately obtuse.

You had to reinstall Windows ENTIRELY in order to get things working NOW.

Yet you claim anything BUT the patch MUST be the cause.  Yes, perhaps it WAS some other 'alteration' to system files that prevented a program install/update.  This apparent cavalier approach to system file integrity bodes ill for future installs too.

Either way, this is [now] a non-issue as you claimed all is well several comments ago.

Oh, I missed that.

I cannot see what relevance that comment has. No-one suggested you do that....;)

The chkdsk C: /f /r  would be a general approach to seeing what was 'wrong'. It would have replaced the uxtheme.dll file for one, and yet might turn up other problems affecting performance of your OS. yrag (almost) always suggests it as a first step, unless there's a clear driver/mechanical/electrical problem.