RegistrationWizard.exe has stopped working

[ilnus]

I recently reinstalled LabVIEW 2011, and I am having a problem with the Registration Wizard. It keeps crashing at startup, either when the computer boots up, or when I manually start it in its program folder. I updated to SP1, but the problem is still there. Here are the details:

Problem signature:
Problem Event Name: APPCRASH
Application Name: RegistrationWizard.exe
Application Version: 1.0.3.71
Application Timestamp: 4c1fd12d
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.23807
Fault Module Timestamp: 5915f98e
Exception Code: c06d007e
Exception Offset: 0000c54f
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

It appears it has something to do with KERNELBASE.dll, but I'm not sure what to do about it. Any help will be appreciated.

[BrandonC1]

Hey ilnus,

Was LabVIEW 2011 working normally prior to the reinstall? If so, have you tried reinstalling again? 

[ilnus]

It was working, but recently I have been unable to compile code for FPGA targets. I did a repair of the FPGA module, but that didn't work. I decided to uninstall everything and reinstall from scratch. The FPGA compiler works now, but the Registration Wizard seems to be broken. I didn't want to reinstall again, since that will take a long time, and I already have the essential modules working. I just want to know if there is a way to repair/reinstall just the Registration Wizard, since it doesn't show up on the list of repairable software.

[BrandonC1 · Accepted solution]

I found a workaround here on the forums. Let me know if this is an acceptable fix, or if it doesn't work for your computer. 

https://forums.ni.com/t5/LabVIEW/Registration-Wizard-Running-at-100-CPU-After-LabVIEW/m-p/2254900#M7...

[ilnus]

That actually worked! I saw this post before, but didn't try the solution because I didn't have the 100% CPU issue, so I thought it was unrelated. Thank you BrandonC1!

[BrandonC1]

No problem, happy to help!