wupdate not working

[NewsArchive]

Hello,

I feel like an idiot because I've used wupdate many many times but for some
reason it's simply is not working for me.

I keep getting an error that an application is not associated with wupdate.

Here's the script:

Install Web Update Client "[SB_LIB]\wupdate.exe" to
"%_SB_INSTALLDIR%\wupdate.exe"

Is that not right?

SB 7.4.3313
Clarion 8
Windows 7 Pro 64 bit

Thanks!

Don

[NewsArchive]

Donald,

1. make sure you compile a 32-bit installer (not 64-bit and not hybrid).

2. make sure you installer requests "requireAdministrator" privileges.

3. in your web update installer package, use the same Product GUID.

Andrea

[NewsArchive]

What's weird is this is the exact same script that was working just a week
ago. The only changes were a new SB version and the app was compiled with
Clarion 8. Otherwise, everything is the same.

Don

[NewsArchive]

Product GUID is the same. I'm at a loss here. Absolutely do not know why
it is not working.

Don

[NewsArchive]

I checked the wupdate.sb7 file and the only thing I can see that's odd is
that it has not been compiled with version 3314. I do not know if that
makes any difference.

Don

[NewsArchive]

I have checked the registry values at
HKLM\Software\Lindersoft\WebUpdate\AppPaths and everything looks fine.

GUID matches. It simply does not work.

Don

[NewsArchive]

Hi Don,

Nothing changed in SB7 here. Just for fun, rollback to the previous SB7
version (use the rollback feature from your SetupBuilder Start menu) and I
am sure you'll see the very same message.

So there must be something in your latest project that causes it.

If you are interested, send your initial .sb7 project and your web update
installer .sb7 project to our Support and we can tell you what causes it.

Friedrich

[NewsArchive]

BTW, did you really check this key:

HKLM\Software\Lindersoft\WebUpdate\AppPaths

It should be under the following node on your x64 machine:

HKLM\Software\Wow6432\NodeLindersoft\WebUpdate\App Paths

If you see it under the 64-bit branch, then you compiled a 64-bit mode
install (not correct in this case).

Friedrich

[NewsArchive]

That's weird. It is not showing up on the Wow6432 side. But I have it set
to compile in 32 bit (See Attachment)

Don

[NewsArchive]

Don,

> That's weird. It is not showing up on the Wow6432 side. But I have it
> set
> to compile in 32 bit (See Attachment)

Then I think you switch in the script to 64-bit processing mode (e.g. to
read a 64-bit registry key) and forgot to switch back to 32-bit?

Friedrich

[NewsArchive]

Yep, you are absolutely right!!! I commented out this script and
everything started working as normal:

Set Variable %IS_X64% to FUNCTION:Get System Info(WOW64 Status)
If %IS_X64% Equals "1" Then
Enable x64 Support
Edit Registry (Create/update key and value)
"HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserLis t" PDManager
Else
Edit Registry (Create/update key and value)
"HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon\SpecialAccounts\UserLis t" PDManager
End

What am I missing to put it back into 32 bit mode?

BTW, I would have never caught this without your Wow6432 comment! I forgot
which side of it was 32 / 64...

Don

[NewsArchive]

Nevermind....I found it! THANK YOU FRIEDRICH! THANK YOU ANDREA! (You were
right all along!)


Don

[NewsArchive]

> Nevermind....I found it! THANK YOU FRIEDRICH! THANK YOU ANDREA! (You
> were right all along!)

:)

Friedrich