64 Bit Windows won't start

When I try to start WL7 64 in Windows 10, the program doesn’t execute. If I look at TaskMgr, Wavelab.exe appears for 2 seconds, then disappears.

The 32 bit version works as usual.

Perhaps related: this started after I had trouble installing the WL9 trial. See this topic:

https://www.steinberg.net/forums/viewtopic.php?f=244&t=98194

How do I fix this?

TIA,

—JC

Anyone? PG?

TIA,

—JC

No idea, sorry. WaveLab 7 was never tested for Windows 10.

What about where you wrote:

Start Registry Editor (Regedt32.exe), and then create the following path and keys in the registry:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

Create keys:
Logging : voicewarmupx
Debug=dword:00000007

Quit Regedt32.exe

Try to install WaveLab.

Is it possible that ‘undoing’ those changes might help?

I don’t think so, because the installer of WaveLab 9 is a different technology that in past WaveLab versions.
This means, the parameter you mention, should have no influence.
BTW, not tempted to switch to WaveLab 9?

I -am- tempted to get WL9. I’m broke right now. So far, I’m having no trouble using the 32 bit version of WL7 so I guess I’m OK until I can get the upgrade.

I have to say that it’s disconcerting for it to stop working right after I ran the WL9 install. It -was- working fine under Windows 10. I understand it’s not your responsibility -but- things don’t happen for no reason…

Best,

—JC

PG: Where are the logs stored when Windows creates a Problem Report? I just noticed that Windows Problem Reporter is firing up when I try to start WL7/64.

TIA,

—JC

Not sure, but try to run eventvwr.msc

Below are 3 events from the Event Viewer.

  1. Seems to be an error generated from WL7/32… although WL7/32 does run properly. This may be unrelated to the problem I’m having with WL7/64 but I include it for thoroughness.

  2. Is the Information event raised when I try to start WL7/64.

  3. Is the actual Error event raised at exactly the same moment when I try to start WL7/64.

Hope these give you some insight.

Thanks in advance,

—JC



Log Name: Application
Source: SideBySide
Date: 7/8/2016 4:28:01 PM
Event ID: 35
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Sandybridge
Description:
Activation context generation failed for “C:\Program Files (x86)\Waves\Applications\wlc.exe”.Error in manifest or policy file “C:\Program Files (x86)\Waves\Applications\WavesQtLibs_4.8.2_Win32_Release\WavesQtLibs_4.8.2_Win32_Release.MANIFEST” on line 8. Component identity found in manifest does not match the identity of the component requested. Reference is WavesQtLibs_4.8.2_Win32_Release,processorArchitecture=“AMD64”,type=“win32”,version=“1.0.0.0”. Definition is WavesQtLibs_4.8.2_Win32_Release,processorArchitecture=“x86”,type=“win32”,version=“1.0.0.0”. Please use sxstrace.exe for detailed diagnosis.
Event Xml:



35
2
0
0x80000000000000

2654
Application
Sandybridge



WavesQtLibs_4.8.2_Win32_Release,processorArchitecture=“AMD64”,type=“win32”,version=“1.0.0.0”
WavesQtLibs_4.8.2_Win32_Release,processorArchitecture=“x86”,type=“win32”,version=“1.0.0.0”
















C:\Program Files (x86)\Waves\Applications\wlc.exe
C:\Program Files (x86)\Waves\Applications\WavesQtLibs_4.8.2_Win32_Release\WavesQtLibs_4.8.2_Win32_Release.MANIFEST
8















Log Name: Application
Source: Windows Error Reporting
Date: 7/9/2016 3:09:51 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Sandybridge
Description:
Fault bucket -517892555, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: WaveLab7_64.exe
P2: 7.2.1.600
P3: 4eeaeefe
P4: StackHash_59d8
P5: 0.0.0.0
P6: 00000000
P7: PCH_E1_FROM_WaveLab7_64+0x00000000006E275F
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
C:\Users\suntower\AppData\Local\Temp\WER4B44.tmp.WERInternalMetadata.xml
C:\Users\suntower\AppData\Local\Temp\WER4CCB.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CFB.tmp.hdmp
C:\Users\suntower\AppData\Local\Temp\WER4D5A.tmp.WERDataCollectionFailure.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WaveLab7_64.exe_cb92884ecb4012283e28f9fba93cdab8215a3fb6_38c593d3_0d9d4d57

Analysis symbol:
Rechecking for solution: 0
Report Id: f1d34346-0e92-4270-aa43-cd7715ef9ec6
Report Status: 8
Hashed bucket: 6008a70ada9bae56a1d669ac341b65c6
Event Xml:



1001
4
0
0x80000000000000

2662
Application
Sandybridge



-517892555
5
BEX64
Not available
0
WaveLab7_64.exe
7.2.1.600
4eeaeefe
StackHash_59d8
0.0.0.0
00000000
PCH_E1_FROM_WaveLab7_64+0x00000000006E275F
c0000005
0000000000000008



C:\Users\suntower\AppData\Local\Temp\WER4B44.tmp.WERInternalMetadata.xml
C:\Users\suntower\AppData\Local\Temp\WER4CCB.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\Temp\WER4CFB.tmp.hdmp
C:\Users\suntower\AppData\Local\Temp\WER4D5A.tmp.WERDataCollectionFailure.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WaveLab7_64.exe_cb92884ecb4012283e28f9fba93cdab8215a3fb6_38c593d3_0d9d4d57


0
f1d34346-0e92-4270-aa43-cd7715ef9ec6
8
6008a70ada9bae56a1d669ac341b65c6

Log Name: Application
Source: Application Error
Date: 7/9/2016 3:09:51 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Sandybridge
Description:
Faulting application name: WaveLab7_64.exe, version: 7.2.1.600, time stamp: 0x4eeaeefe
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000013c03a90
Faulting process id: 0x29a8
Faulting application start time: 0x01d1d9ca07cf6d35
Faulting application path: C:\Program Files\Steinberg\WaveLab 7\WaveLab7_64.exe
Faulting module path: unknown
Report Id: f1d34346-0e92-4270-aa43-cd7715ef9ec6
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
2
100
0x80000000000000

2661
Application
Sandybridge



WaveLab7_64.exe
7.2.1.600
4eeaeefe
unknown
0.0.0.0
00000000
c0000005
0000000013c03a90
29a8
01d1d9ca07cf6d35
C:\Program Files\Steinberg\WaveLab 7\WaveLab7_64.exe
unknown
f1d34346-0e92-4270-aa43-cd7715ef9ec6





No clue. In one of the report, some Waves module is involved, though.
Anyway, you say WL7/32 is running fine isn’t it?

Resolved. The solution was to RE-install the Windows 8 patch.

I have no idea why it worked. Just tried it as a Hail Mary, thinking that the WL9 installer had ‘undone’ something.

—JC