File Explorer won't open since Win 10 version 1809

from Stardock Forums

I have a WinForms application that uses Stardocks WindowBlinds skin. Since the latest Windows 10 update build 1809 I can't use the basic System.Windows.Forms.OpenFileDialog without it crashing on 0x80040111 (CLASS_E_CLASSNOTAVAILABLE) exception (see stack below). This issue also affects SaveFileDialog.

I have tried everything I could think of such as:

  1. Tried to use all the different flags.

  2. Tried to exclude the open file dialog from the skin.

  3. Different suggestions from other forums to disable high contrast and other stuff for issues that also get COM exception like mine.

The only thing that made it work was to use the AutoUpgradeEnabled as false and then the dialog gets a very old Windows 7 skin.

anyone else having the same issue?

The full stack:

Delegate method b__0 with args System.Object[] threw an exception Creating an instance of the COM component with CLSID {C0B4E2F3-BA21-4773-8DBA- 335EC946EB8B} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)). System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {C0B4E2F3-BA21-4773-8DBA-335EC946EB8B} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)). at System.Windows.Forms.SaveFileDialog.CreateVistaDialog() at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner) at System.Windows.Forms.FileDialog.RunDialog(IntPtr hWndOwner) at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) at System.Windows.Forms.CommonDialog.ShowDialog()

Thanks,

Adar

windowblinds
11,667 views 12 replies
Reply #1 from Stardock Forums Top

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

The product we have for custom app skinning is called DirectSkin:

https://www.stardock.com/corporatesolutions/directskin/

If that is indeed what you are using (and the only thing we support for custom app skinning), one needs to still have an active contract for support.  If that is the case, that you need support and are under an existing support contract, please place a ticket here:

https://esupport.stardock.com/index.php?/Tickets/Submit

If you do not have a support contract, you can use the first link to contact sales.

----------------
Sean Drohan
Stardock Customer Service Manager

 

 

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #5 from Stardock Forums Top

Hi,

I have talked to Stardocks supports and using their latest DirectSkin files and using SetVersion flag 7000, the issue has been resolved.

They have fixed it recently.

 

Good luck!

Adar

Reply #6 from Stardock Forums Top

Thanks Adar. We pointed this link to Stardock team on our issue and tried SetVersion flag 7000 with new wbocx.ocx they provided for other issue, but that does not help us. Hopefully they should get back with proper solution.

Reply #7 from Stardock Forums Top

Hi Adar,

Currently we have reported our issue to Startdock team and also pointed this link. If you know on the latest skin files received from Stardock to resolve your issue, do you know what changes have they made on the skinning files? Have you got wbocx.ocx control or just skinning files? If possible, may I know the name of files you got from Stardock as a solution?

 

Thanks.

Reply #8 from Stardock Forums Top

Hi Stardock team,

If you are reading this post, can you please reply on our ticket #WYK-507-40998? We have the same issue as reported in this thread and we haven't got any skinning files as mentioned by Adar for resolving this issue.

Thanks.

 

Reply #9 from Stardock Forums Top

Hi,

Wbocx.ocx files version 10.0.1.0 have the fix you are looking for.

Ask Stardocks to send you the latest version.

 

Good luck,

Adar

Reply #10 from Stardock Forums Top

Thanks Adar for confirming the file version you have. I got the same version from Stardock. Still we have the following error:

I set 7000 version in code as well.

directSkin.SetVersionExpected(7000); //Enables DirectSkin 7 defaults.

I set 7000 version in code as well. Does the position of above line matter in initializing stardoc ocx control?

************** Exception Text **************

System.Runtime.InteropServices.COMException (0x80040111): Creating an instance of the COM component with CLSID {C0B4E2F3-BA21-4773-8DBA-335EC946EB8B} from the IClassFactory failed due to the following error: 80040111 ClassFactory cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE)).

   at System.Windows.Forms.SaveFileDialog.CreateVistaDialog()

   at System.Windows.Forms.FileDialog.RunDialogVista(IntPtr hWndOwner)

   at System.Windows.Forms.FileDialog.RunDialog(IntPtr hWndOwner)

   at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner)

   at System.Windows.Forms.CommonDialog.ShowDialog()

Reply #11 from Stardock Forums Top

I use this line right after initializing the skin.

Did you remember to run regsvr32 on the new ocz files? Maybe the old ocz is registered on your machine. 

 

I think you should talk to Stardocks if it doesn't work after trying the above. 

 

Adar

Reply #12 from Stardock Forums Top

Thanks Adar for replying on my post. I have posted same thing to Stardock support but it takes some time on getting response from them.  

I followed below steps for installing new ocx.

WBOCX32_10010_02042019\32\wbocx.ocx --> Copied to "C:\Windows\SysWOW64" folder
WBOCX32_10010_02042019\32\wbocx32.ocx --> Didn't copy this file
WBOCX32_10010_02042019\64\wbocx.ocx --> Copied to "C:\Windows\System32" folder
WBOCX32_10010_02042019\64\wbocx32.ocx --> Didn't copy this file

C:\Windows\System32>regsvr32 /u wbocx.ocx
C:\Windows\SysWOW64>regsvr32 /u wbocx.ocx

C:\Windows\System32>regsvr32 wbocx.ocx
C:\Windows\SysWOW64>regsvr32 wbocx.ocx

Please correct me if I am following wrong steps.