A Small

I'm trying to run SUA on XP, but it just won't launch an application, not even Notepad. After selecting Launch, it tries to execute the named application (gets as far as "WorkingDir: C:\WINDOWS" in the Debug Info) and then Notepad throws an Application Error:

<ICON_STOP> "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." [OK]

Clicking OK, Notepad returns "-1073741502". Looking at the XML log in my temporary area, it reports (4 times):

<avrf:logEntry Time="2007-01-03 : 16:09:14" LayerName="LuaPriv" StopCode="0x3304" Severity="Warning">
<avrf:message>Initialization failed.</avrf:message>
<avrf:formatmessage>Profile: The USERPROFILE environment variable could not be found</avrf:formatmessage>
<avrf:parameter1>3d3398 - N/A</avrf:parameter1>
<avrf:parameter2>521 - N/A</avrf:parameter2>
<avrf:parameter3>0 - N/A</avrf:parameter3>
<avrf:parameter4>0 - N/A</avrf:parameter4>
</avrf:logEntry>

But adding a USERPROFILE entry to my environment variables and closing/restarting SUA made no difference. (It appears in a new Command Prompt "SET" command).

SUA is version 1.0.1.700, Windows XP is patched to date, and my account has admin rights. Installed development environment is VC6. The Application Verifier behaves similarly if I set the LUA checkbox.

Second time around, attempting to close SUA gave this dump:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Configuration.ConfigurationErrorsException: Failed to save settings: A configuration file cannot be created for the requested Configuration object. ---> System.Configuration.ConfigurationErrorsException: A configuration file cannot be created for the requested Configuration object.
at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
at System.Configuration.Configuration.Save()
at System.Configuration.ClientSettingsStore.WriteSettings(String sectionName, Boolean isRoaming, IDictionary newSettings)
--- End of inner exception stack trace ---
at System.Configuration.ClientSettingsStore.WriteSettings(String sectionName, Boolean isRoaming, IDictionary newSettings)
at System.Configuration.LocalFileSettingsProvider.SetPropertyValues(SettingsContext context, SettingsPropertyValueCollection values)
at System.Configuration.SettingsBase.SaveCore()
at System.Configuration.SettingsBase.Save()
at System.Configuration.ApplicationSettingsBase.Save()
at LUAAnalyzerViewer.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SUAnalyzer
Assembly Version: 1.0.1.700
Win32 Version: 1.0.1.700
CodeBase:
file:///C:/Program%20Files/Standard%20User%20Analyzer/SUAnalyzer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Deployment
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.



Re: Application Compatibility for Windows Vista SUA fails immediately even on Notepad

Oliver Lundt - MSFT

I'm stumped have no idea what would be causing this!! And it looks like a lot of people have looked at this posting with out responding, so they are stumped too. I'm running SUA version 1.0.5428 that's a difference. I installed from the ACT 5.0 tool kit. Does SUA from Vista work with notepad I ran this scenario and it works no problem. Not a single SUA issue or failure to launch the application.

SUA does require windbg. Do you have this installed Make sure both are either 32bit or both are 64bit installs. I don't think it works to well if one is the other.

But like I'm stumped and just guessing here!!






Re: Application Compatibility for Windows Vista SUA fails immediately even on Notepad

A Small

SUA on Vista (32-bit running in WMWare) works.

Under XP I did need to install windbg, but it still fails. All the installers were suffixed x86, so should be a matched set. As the development environment is on XP, it would be much easier for me if the SUA worked on that platform.

Has anyone else had problems getting this to work in XP