Windows 10: DLL file in System32 and Excel problem

Good afternoon -


I don't know if this is a Windows or Office question, so I'm asking it in both sections.


I'm experiencing a difficult problem with Excel, in Office Pro 2019, on a desktop computer running Windows 10 Pro, version 1809. This started last Tuesday morning (Aug27), and not after a software update. Aug 29 a large update was installed by Windows, but this did not remedy the problem. In researching others who have experienced difficulties like this, I have not loaded any apps from Google or Dropbox (for some folks, those apps interfered/caused conflict with Office). No add-ins have been loaded to any component of Office 2019 Pro. Only Excel is impacted - all other Office components are working fine. Also, this problem showed up out of the blue - Excel had been working fine on Aug 26.


I can launch and use Excel in the Administrative account. But, if I log-in to my user account (non-admin privileges), when I launch Excel (either by clicking on the icon in the Start menu, or by double-clicking an Excel file in Explorer), the Excel icon appears on the Taskbar, but it is orange, and I cannot open/display the file (or even the Excel start screen where you can choose a recently opened file, or create a new blank document, etc.). I can right-click on the Taskbar icon to close Excel, or I can open Task Manager and choose to close it via End Task.


I have run the on-line Office Repair Tool, but that did not fix the problem. I can start Excel in Safe mode, and it works as it should.


I've looked at the Events Viewer log of errors, and all previous errors (from Aug. 28 and earlier) appear to have been removed by the Office Repair Tool today. The only errors reported are timestamped from after the Windows Update and the use of the Office Repair Tool. I have since logged in to the non-admin account and 'launched' Excel, and that generated these Error reports in Event Viewer:


1 - "Windows cannot load the extensible counter DLL "C:\WINDOWS\system32\sysmain.dll" (Win32 error code The specified module could not be found.)."

2 - "Unable to open the Server service performance object. The first four bytes (DWORD) of the Data section contains the status code."


When I look in the directory: C:\Windows\System32\

I find these 2 files next to each other:

sysmain.dll.mui ~7kb, created/modified back in May 2019

sysmain.dll ~980kb, created/modified Aug. 29 (when I ran the Office Repair Tool)


So the sysmain.dll file appears to exist, but for some reason it is not loadable from the non-admin account.


Another note, when I check these same file locations on my laptop, running Windows 10, but only the basic version of Office 2019, the sysmain.dll.mui file is not in the System32 folder, but here:

C:\Windows\System32\en-US\sysmain.dll.mui


Could this be part of the problem?


Any suggestions on how to fix this/these errors? And if a DLL is unloadable/not found, why does Excel work in one user account, but not another? Thank you for helping me!


Claudia

:)

 

dll file not found after Creator's Update, Code Execution Cannot Proceed

Hi Aberfoyle,

It is possible that the
.dll file was corrupted during the update causing the error to occur.
To better assist you, kindly find the
.dll file
in
c:\Windows\System32. If you can find the
.dll file, it means that we need to
register
your
.dll file
to your
Operating System
for it to
work. To do this, we need to
unregister
the
.dll file
first and
re-register
it. Here are the steps on how to do so:

To unregister the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 /u c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

To re-register the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

If you cannot find the
.dll
file in
c:\Windows\System32,
kindly run these methods of troubleshooting
so that we will know if the issue is within/not within the
Operating System:

Method 1:
Run SFC Scan.  

SFC
will
scan
and
run
an
automatic repair
to any
corrupted system files
that it will detect. We suggest that you perform it twice. To run an
SFC scan, follow these steps:  

• 
  Run
  Command Prompt as Administrator.  
  
• 
  Type
  sfc /scannow
  and hit
  Enter.   
  

Note:
Kindly run
SFC twice or thrice
and check for results before you proceed to the next method.

Method 2: Clean Boot.

Clean Boot
will
stop or disable
the
applications
that are running in your
computer's background.
To perform a
Clean Boot, click
here.

Note:
Reset the computer back to
Normal Mode
once you are done with the troubleshooting by following the section
"How to reset the computer to start normally after clean boot troubleshooting"
from the same article.

After performing these
methods of troubleshooting
and still the issue persists, we suggest that you contact your
computer/laptop manufacturer
for further assistance.

Update us on how it goes.

Regards.

 

Rundll32.dll?

Make sure to use an adminstrative command prompt.

Try this: ICACLS "c:\windows\system32\rundll32.dll" /T /grant Everyone:F or ICACLS c:\windows\system32\rundll32.dll /T /grant Everyone:F
Can't remember if it is with, or without, quotes.

But, why do all this... try FileAssassin by Malwarebytes, if you are trying to delete the files, but be careful, if you delete the Rundll32.dll files your OS may take a cr*p on you.

 

nv4.dll problem

ok, after 3 hs on google i think i found a solution, i hope, i download a nv4.dll file and put on c..windows..system32

that i was found in another forum and the guy who have the problem can fixed that way, i hope me too
i recently play 10 minutes aprox without crash. tonight y play hours to check it and i hope this works fine.