View original (French)

Invalid DLL at startup Windows 10

Solved
Jymmy26 Posted messages 8 Status Member -  
Jymmy26 Posted messages 8 Status Member -
Hello, ... at Windows 10 startup after the programs load a window: "Problem at startup of C:\Users\SCHAEF~1\CNMSSC~1.DLL configure Windows 10 to start automatically is not a valid application." I don't know what to do to resolve this... if someone would be so kind as to suggest a solution. It seems to be a virus? Thank you.

1 answer

Answer 1 / 1
Malekal_morte- Posted messages 178136 Registration date   Status Moderator, Security Contributor Last intervention   24 711
 
Hi,

It's related to Canon, apparently.
Reinstall it.

--
Like the angel you are, you laugh creating a lightness in my chest,
Your eyes they penetrate me,
(Your answer's always 'maybe')
That's when I got up and left
2
Jymmy26 Posted messages 8 Status Member
 
Thank you Malekal, I will try to reinstall...
0
Jymmy26 Posted messages 8 Status Member > Jymmy26 Posted messages 8 Status Member
 
Unfortunately, after completely uninstalling and reinstalling all my Canon drivers, the problem persists... Thanks anyway Malekal...
0
Jymmy26 Posted messages 8 Status Member > Jymmy26 Posted messages 8 Status Member
 
I finally made it:
1 you need to figure out which software the blocking dll corresponds to, and for me, thanks to Malekal, it was Canon.
2 I equipped myself with the software for my Canon printer and those for my camera, as well as driver updates on Canon's site for my hardware type
3 I uninstalled all Canon programs using the Add/Remove Programs menu in the Control Panel
4 I rebooted my computer each time
5 I then opened CCleaner, Tools section, startup... and there I found a dll entry that remained in the list and that corresponded to Canon, so I deleted it because I should no longer have a dll at startup for Canon even though I had removed my Canon software...
6 I rebooted the PC and miracle, no more startup dll issue
7 I reinstalled my Canon software with their driver updates...

it worked! Thanks to Malekal for identifying the dll... there you go, good luck to you if needed... it took me some patience.
0