View Single Post
  #2  
Old January 11th 19, 01:40 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Missing dll file

swalker wrote:
Attempting to start system and this message appears after the sign in
screen on Win7

"There was a problem starting C:|Windows\system32\nvspcap64.dll"

Another longer message in a sseperate box said
"z:\Users\xxxxxxxxxxx\Desktop refers to a location that is
unavailable........"

Doing a search using Everything I found that the missing file exists
in several places on the computer, either on C or Z.
(Z is my SSD for data.)

I do have a clone of the system that is a couple of months old and
wonder if I would copy the missing file from the appropriate folder of
the clone and copy it to the current drive in use.

Would this solve the problem?

Thanks for any help.


https://forums.geforce.com/default/t...rror/?offset=3

"nvspcap64.dll is related to GeForce Experience,
try uninstalling/reinstalling GFE. "

I don't have Geforce Experience installed on my NVidia system,
and that's why I couldn't find a sample of that file.

You could look in Control Panels : Programs and Features and
see if Geforce Experience is a separate item. Select it and
see if it has a "Repair" option. Once repaired, try a reboot.

The NVidia driver package tries to unpack on the C: drive
in a temporary folder. But it probably also deletes itself
when finished. One would hope that a .msi file is cached
somewhere which corresponds to the NVidia installer and
that it supports "Repair" as an option. Rather than just
"Remove" via running some uninst file in the folder it's in.

So the steps would be:

1) Installer unpacks into a temp folder. It
prompts for a name and most people would accept the
default.
2) Installer allows you to select what gets installed.
3) After install is finished and you dismiss the window,
the temporary folder should be removed.

I've also had NVidia materials where the unpacked stuff
sticks around, so their software is not always "consistent"
with respect to removal. That might have been the CUDA SDK.

That thread has more examples of "responses" to that error.
It could be that it's a startup item and it's gone missing
for some reason.

Paul
Ads