Method faild w/unexspected error code 193.

Use to work.

from Stardock Forums

Logon Studios Vista was working fine until I downloaded a skin. Ever since I DLed the skin I get this Error:

 

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

************** Exception Text **************
System.InvalidOperationException: Method failed with unexpected error code 193.
   at System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
   at System.Security.AccessControl.FileSystemSecurity..ctor(Boolean isContainer, String name, AccessControlSections includeSections, Boolean isDirectory)
   at System.Security.AccessControl.FileSecurity..ctor(String fileName, AccessControlSections includeSections)
   at h.a(String A_0, Boolean A_1)
   at b.c()
   at b.c(Object A_0, MouseEventArgs A_1)
   at System.Windows.Forms.Control.OnMouseDoubleClick(MouseEventArgs e)
   at System.Windows.Forms.ListView.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.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
LogonStudioVista
    Assembly Version: 1.0.1.7
    Win32 Version: 1.0.1.6
    CodeBase: file:///C:/Program%20Files%20(x86)/Stardock/Object%20Desktop/LogonStudio/LogonStudioVista.exe
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
AxInterop.WBOCXLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Stardock/Object%20Desktop/LogonStudio/AxInterop.WBOCXLib.DLL
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Interop.WBOCXLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/Stardock/Object%20Desktop/LogonStudio/Interop.WBOCXLib.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.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.

logonstudio
7,235 views 11 replies
Reply #1 from Stardock Forums Top

I have the same problem, I am running Vista 64, but after coming here using Impulse for some reason it just worked.  Seems that it errors out alot, just try a few times and eventually it will work.

Reply #2 from Stardock Forums Top

I am getting the same error in Vista 64 now. Is there a fix? It doesn't matter what skin I try.

SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

I am getting the same error in Vista 64 now. Is there a fix?

Reply #5 from Stardock Forums Top

I'm also getting the same error.  I'm running Vista 64.  I installed Object Desktop Ultimate, then installed LogonStudio and applied one skin.  Since then I get the same error "Method faild w/unexspected error code 193" each tme I try to apply any other skin, including the Windows default.  Has anyone heard of a fix?  Multiple uninstall/reinstalls have not worked.

Reply #6 from Stardock Forums Top

I posted this in another thread but here is what worked for me below.

I found if you load the latest icon packager and then open up one of the default logons from C:\Program Files (x86)\Stardock\Object Desktop\LogonStudio\DefaultLogons then apply it it seems to work fine with every logon after that. Go to the directory and launch the logons from there do not try and open them from the app until you at least launch one of the default logons from C:\Program Files (x86)\Stardock\Object Desktop\LogonStudio\DefaultLogons directly from windows explorer.  It may take a few tries at aplying the logons.. But... The latest Icon Packager is a bit buggy... I found that my Outlook Icon that is pinned to my start menu stopped working and no longer opens outlook. Then again I use my quick launch outlook icon anyways so it isn't too big of a deal. Here is the kicker though you can't run the logon Vista to change them you go to the directory for the defaul logons to apply them but once you apply the default ones you can add ones you want when the Logon studio Vista launches from opening the default logons.

I have uninstalled and re-installed all the applications serveral times and it works every time following the steps I listed.

 

I hope that made sense.

Reply #8 from Stardock Forums Top

I would like to also verify that this workaround does work.  Thanks for the answer until the bug is found.

Reply #9 from Stardock Forums Top

OK - this workaround will NOT apply to let me return to the default login screen. I want to return my login screens to default to troubleshoot an issue with my fingerprint reader. (Want to apply the default and then uninstall LogonStudio so that I can rule out an issue with logonstudio)

Reply #10 from Stardock Forums Top

Quoting IanTyger, reply 9
OK - this workaround will NOT apply to let me return to the default login screen. I want to return my login screens to default to troubleshoot an issue with my fingerprint reader. (Want to apply the default and then uninstall LogonStudio so that I can rule out an issue with logonstudio)

 

I found that if you follow the instructions I made there you can apply the default after you open one of the Stardock logons.

Reply #11 from Stardock Forums Top

Thanks for the workaround.  It worked on my first try and I've been able to switch to several different logon screens now.  Looking foward to the bug fix on this one.  I am on Vista Ultimate 64-bit like the other posters in this thread.

As a further note, I didn't have Icon Packager installed at all, before or after I did the workaround, so I would say for those who don't have it installed, there is no need to do so.