Failure to call MS Word / Excel with OLE error

1. Open new file (empty one) in Excel.
2. Go to the Home and press Recent files.
3. Press right click of the mouse and choose to remove all the files that you've ever opened with the same name of the file you're just trying to open. Don't use the search option as it opens the file instead of just searching and marking it. You need to look for the file that was open for every single day you could have had it open.
4. After you make you ALL of the previous files are removed open new file again.
5. Instead of normally closing the file open Task Manager and End Task for Microsoft Excel.
6. Try to open your destination file. If the problem persists keep repeating no. 3,4 and 5 until your destination file will eventually open.

tigerpanda said:

Hi,

After upgraded to Windows 11 24H2, my application failure to call MS Word / Excel with OLE error (Error 35).

Master image is same one but this issue not encountered on all PC.

It's know issue or any fix on it ?

Thanks

Click to expand...

tigerpanda said:

Master image is same one but this issue not encountered on all PC.

Click to expand...

antspants said:

Are you talking Microsoft 365, Office 2021? What version of Office?



What master image? Do you mean the WIndows installation?

Click to expand...

SoFine409 said:

1. Open new file (empty one) in Excel.
2. Go to the Home and press Recent files.
3. Press right click of the mouse and choose to remove all the files that you've ever opened with the same name of the file you're just trying to open. Don't use the search option as it opens the file instead of just searching and marking it. You need to look for the file that was open for every single day you could have had it open.
4. After you make you ALL of the previous files are removed open new file again.
5. Instead of normally closing the file open Task Manager and End Task for Microsoft Excel.
6. Try to open your destination file. If the problem persists keep repeating no. 3,4 and 5 until your destination file will eventually open.

I found this after a quick search. Hopefully it will help you. Others might have other solution for you to try.

Click to expand...

tigerpanda said:

Programmer told me it's OLE error "Error code 35".

Click to expand...

• Log in as local admin.
• Unseal the image if in maintenance/sealed mode.

• Open Word and Excel once to complete first-run setup.
• Match Office bitness to your calling app:
  
  ​
  • 32-bit PowerBuilder → Install 32-bit Office
  • 64-bit PowerBuilder → Install 64-bit Office

• Word:
  
  Code:

  "C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE" /regserver

• Excel:
  
  Code:

  "C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE" /regserver

• (Adjust path if Office installed elsewhere — Office16 applies to M365 & Office 2016–2021)

• Word:
  
  Code:

  HKEY_CLASSES_ROOT\Word.Application
  HKEY_CLASSES_ROOT\Word.Application\CLSID
  HKEY_CLASSES_ROOT\CLSID\{000209FF-0000-0000-C000-000000000046}\LocalServer32

• Excel:
  
  Code:

  HKEY_CLASSES_ROOT\Excel.Application
  HKEY_CLASSES_ROOT\Excel.Application\CLSID
  HKEY_CLASSES_ROOT\CLSID\{00024500-0000-0000-C000-000000000046}\LocalServer32

• Ensure LocalServer32 path points to the correct WINWORD.EXE / EXCEL.EXE

• Run: dcomcnfg
• Navigate to:
  
  
  Component Services → Computers → My Computer → DCOM Config​
• Ensure Microsoft Word & Microsoft Excel have Launch/Activation rights for INTERACTIVE or Authenticated Users.
• If AppLocker/WDAC is in use, whitelist:
  
  Code:

  WINWORD.EXE
  EXCEL.EXE
  VBE7.DLL
  Office COM DLLs under C:\Program Files\Microsoft Office\root\OfficeXX\

• Test Word:
  
  Code:

  Set objWord = CreateObject("Word.Application")
  objWord.Visible = False
  objWord.Quit

• Test Excel:
  
  Code:

  Set objExcel = CreateObject("Excel.Application")
  objExcel.Visible = False
  objExcel.Quit

• Save each as [.I].vbs[/.I] and double-click — no error = COM works

• For M365 Shared Computer Activation:
  
  Code:

  cscript ospp.vbs /dstatus

• Suppress first-run dialogs via GPO:
  
  
  User Config → Admin Templates → Office 2016 → Skip First Run​

• Run sysprep or Citrix sealing process.
• Push updated master to catalog.
• Test in a new VDI session.