Can't update Impulse or anything else...

Start Impulse.

Update found, logging in, downloading, extracting...  ERROR! 

"There was a problem while Impulse was auto-updating, please try again. Updating/installing of applications will be unavailable until you restart Impulse."

Click OK

"Administrator privileges required for update." 

UAC is OFF. 

Can't update Fences. Can't update WindowBlinds. Can't do anything at all.

 

I remember I had to FORMAT my hard drive and REINSTALL Windows in order to get Impulse to install in the first place (it kept going on about admin rights and such). Now this crap is happening again. There is obviously something on my computer that Stardock doesn't like. How can I find out what it is??

 

30,911 views 45 replies
Reply #2 Top

I'm running the entire ESET Smart Security suite. Nothing unusual.

I tried support the first time around. They were not particularly helpful. I kept getting bounced around between different agents who all told me to try things I had already tried. It wasn't much fun...

Reply #3 Top

garbanz0 ....the first requirement you'll need to provide...for any community support here is to provide as much info as possible as to system specs, etc...eg Which OS, and is it updated [since reinstall]. Admin account or restricted, etc.

Then it's quite possible that another program is interfering [firewall, av, etc] or even failed packet downloading - ISP issues - corrupting the download.

I know it's no help [to you] that millions of people do not strike this issue - BUT that is a specific indicator that the problem MAY very well be with your specific system/install.

The method of problem resolution is for help/support being able to diagnose through replication, or, if not through process of elimination.

The more unique the issue the harder/longer [often] the process of sorting it.

On occasion the error can be server-side but when that's the case there is always a 'flood' of similar errors from other users.  That doesn't appear to be the case here/now...;)

+1 Loading…
Reply #4 Top

I think Jafo's right, garbanz0. Also about the info thing. You didn't mention you'd been on with Support. I've never outguessed those folks as to reason for problems.

Perhaps you could summarize what's been done, and add your ticket number. Names aren't needed. We'd all like to help you have a truly enjoyable experience... after all, we want you here!

So, when you can, see if you can update us with all your machine data as Jafo suggested (he's a pretty fair hand at problem solving - been at it a really long time)/Support info.

Sometimes it's a driver issue/machine issue (and there's a fella "yrag" who's aces at solving those - who stops by to spread cheer).

Don't give up... just be patient, and keep us informed.

Reply #5 Top

Windows 7 Home Premium N x64.

Unrestricted Admin account, UAC off.  

Tried with ESET Smart Security off, but results were the same. 

 

My initial problem involved not being able to install Impulse due to errors about not having admin rights. I sent in logs [#QME-952273] but they didn't help at all.

As per my conversations with support [#ZQY-681319], I tried CleanImpulse.exe, I tried sfc /scannow, I tried running a repair install of Windows. I even ran Impulse in Windows XP running in Virtual Box and it installed fine, further indicating a problem specific to my machine. 

Support finally stopped responding. In desperation, I reinstalled Windows, and as soon as the new, clean OS was up and running, I managed to install Impulse and then WindowBlinds without issue.

That was several months ago. WB has been running fine. I realized yesterday that it wasn't auto-updating, so I opened Impulse. Impulse tried to update, but ran into the same errors about admin rights, and now won't let me update any of my other Stardock apps. 

This all suggests to me that something I have changed or installed since reinstalling Windows has blocked Impulse again. As I look through my list of installed apps, nothing jumps out as particularly intrusive. I do have my uxtheme.dll and related files patched to run unsigned themes, but I can't imagine that's the problem, is it?

 

 

 

Reply #6 Top

Quoting garbanz0, reply 5
This all suggests to me that something I have changed or installed since reinstalling Windows has blocked Impulse again. As I look through my list of installed apps, nothing jumps out as particularly intrusive. I do have my uxtheme.dll and related files patched to run unsigned themes, but I can't imagine that's the problem, is it?

I bet we just solved the problem.

Running sfc /scannow fixes your windows sys files then the msstyles screws it again.

You can't have it both ways.

1. Get rid of the hacked uxtheme.dll and the msstyles crap.

2. Do an sfc /scannow and I bet you never have another problem.

Reply #7 Top

Quoting garbanz0, reply 5
I do have my uxtheme.dll and related files patched to run unsigned themes, but I can't imagine that's the problem, is it?

I would think it likely is. Impulse may be having issues when it detects altered system files.

Reply #8 Top

I restored the originals, Impulse still won't update. Not surprised, hacked theme files don't have much to do with admin rights...

I'll run SFC and see what happens, but it didn't work before, so I don't have high hopes. 

 

Anyway I wouldn't call it crap. There are dozens of professional quality Visual Styles out there for Windows 7 that I enjoy, but there is only one WB skin that I have found that I like (well enough to buy WB in fact!)

 

Reply #9 Top

No luck. 

After Impulse downloads and extracts the update, a command window pops up briefly - I can't see what it's trying to do. That's when the error comes up about Impulse updating. 

---

OK I just downloaded and ran the Impulse installer which worked fine, so now I have the latest version running. But I am now back to the exact same problems I had to begin with. I try to update WB, and I'm told "You must allow Impulse to run as Administrator to continue."

It seems I have to reinstall Windows whenever I want to update my Stardock software. What fun. 

Reply #10 Top

Didn't mean the art, garbanz0 - meant the hack.

Make sure it's off your machine totally before you do the sfc /scannow.

In fact, if I were you, I'd do a  chkdsk /f /r

Takes time to run, but it'll fix just about anything that can be fixed. sfc /scannow will only fix windows system files (the sfc).

Reply #11 Top

Quoting garbanz0, reply 5
I do have my uxtheme.dll and related files patched to run unsigned themes, but I can't imagine that's the problem, is it?

In one word....

YES.

 

An altered [and unsanctioned] IMPORTANT MS Dynamic Library is guaranteed to cause problems.

Reply #12 Top

Unsanctioned, but in my experience, far more reliable than the alternative  :grin:

 

Anyway, as I said, the original files have been replaced, but Impulse still whines... 

Reply #13 Top

Try  chkdsk /f /r  on ALL your peripheral storage as well... it might be lurking. Also, Eset the peripherals as well. Then, if all's well, uninstall Impulse with CCleaner and it's registry stuff as well.

Then reinstall the full impulse client install with firewall/antivirus off, and then don't forget to turn them on again.

 

Reply #14 Top

I'm not uninstalling Impulse! I had to reinstall Windows to install it in the first place!

I'm heading for work now, no time to run chkdsk on my 4.5 TBs of hard drives. Anyway, this is obviously a software issue... 

 

I'll probably just end up formatting my system drive and starting with a fresh install of Windows. I installed a new motherboard last week so I should probably do that anyway... 

Reply #15 Top

Actually, you could have left it to run... it gives you a log at the end of the run. If you decide to format, good luck. But I'd make sure that the other drives don't have any backups that could include the hack... or you'll be back to where you started.

Reply #16 Top
Oh good grief. I told you, there is no hack. I manually swapped patched system files. After I reformat tonight I'll patch my theme files before I install Impulse and see how it goes :)
Reply #17 Top

The term 'hack' was not used except to note that the sys32 file was replaced by another not of MS origin.... not to imply you are a 'hacker', garbanz0. :)  Just trying to help, bud.

I hope it goes well, but I think running chkdsk /f /r might reveal and possibly repair other problems.  

 

Reply #18 Top

Quoting garbanz0, reply 16
I told you, there is no hack.

Actually there IS a 'hack'.

The 'patcher' you use is a reverse -engineered MS DLL [uxtheme.dll] originally manually HACKED to breach MS-imposed restrictions on the use of altered [unsigned] themes.

This 'patch' was systematically 'broken' by MS with subsequent Service Pack releases prompting the hack's author to do-it-all-again.

Quasi-legitimacy was argued [by them] once they'd nutted out how to do the 'patch' in memory rather than a file break-and-distribution which is technically warez.

Although there are a loyal bunch of skinners who use the process it is so limited in it's scope for creativity/diversity that effectively all the skins tend to be so alike to be just plain uninteresting.

Bigger issue is that ANY proggy expecting to find a LEGAL and Legitimate uxtheme.dll [Microsoft's] WILL likely BREAK and/or fail to install or function at all.

UAC 'complaints' will most likely be due to this patching [in memory] locking legitimate programs out of accessing the Library.

I've not even bothered with the patched 'crap' for eons as the method was too featureless, the support did not exist and frankly the people behind it were arseholes.  [old story - dates back almost a decade].

Yes, there are skins for it out there...

and yes, it'll get in the way of 'real' GUI software.

Reply #19 Top

I probably should add that I believe it's 'policy' to not provide support to users of the 'patched' uxtheme.dll.

It's suggested that people approach the 'msstyles' forums instead since the issue is actually with their product....;)

Reply #20 Top
I'd like to point put that WB runs jus fine with patched theme files. As such, IF my theme files are the problem (which indoubt since Impulse still won't update after unpatchingg them), then Impulse is actively creating a problem in anticipation of an imaginary conflict which in fact does not exist, much like WB's treatment of dopus.exe to "fix" other imaginary problems...
Reply #21 Top

OK here we go!

1. Formatted my system drive.

2. Re-installed Windows.

3. Patched my theme files.

4. Installed Impulse, installed WindowBlinds, all is well.

 

;P  

Reply #22 Top

Quoting garbanz0, reply 21
OK here we go!

1. Formatted my system drive.

2. Re-installed Windows.

3. Patched my theme files.

4. Installed Impulse, installed WindowBlinds, all is well.

Ah...looks like you got the sequence right then....;)

Good to see...;)

Reply #23 Top

Oh, suddenly the problem is moot?

I really don't feel that anything has been solved here...

Reply #24 Top

Quoting garbanz0, reply 23
I really don't feel that anything has been solved here...

Yes it has...you said your system is fine now...so it's "solved".

 

To reiterate...this wasn't a problem caused by WB, but it was WB that showed up the problem caused by the use of a hacked MS dynamic link library that is unsupported by Microsoft....;)

[Stardock's software is 'endorsed' by MS as Stardock is a certified Gold partner.]

Reply #25 Top

Sorry bud, you're misreading my post.

I patched (hacked) my theme files PRIOR to installing WB via Impulse, and all worked fine. The theme files were NOT the issue.

The problem is the crap software called Impulse. If Stardock would just distribute proper installers like everybody else, then all would be well in the world...