No matter how long one works with MS Windows one still stumbles.
I have a new machine and I have been installing quite a few applications and just found out Google Chrome and Mozilla.Org Firefox are no longer working.
SysInternals – Process Monitor
Checked Event Viewer, but nothing and so downloaded SysInternals’s Process Monitor and trained it at my google Path.
- The give away is that netutils.d.dll, srvcli.dll, wkscli.dll, Samcli.dll can not be found
Launched OS Command Shell and checked path by issuing “path”
Placed C:\Windows\System32 squarely in front of everything.
SysInternals – Process Monitor – Post Correction
Once changes made, we can see that the effect of the changes:
CreateFile – NAME NOT FOUND
CreateFile – SUCCESS
- Attempt to access wkscli.dll from the local folder failed
- Hence, the system accessed via C:\Windows\SysWOW64
I know it is a far cry from where we used to be, but the System Path and centralized registry can still be a bit brittle and unforgiving.