Hi Wesley - sorry for delay, been busy. Have had mixed success as
follows: Using 'regedit' located NVIEW REG_SZ rundll32.exe
nview.dll,nViewLoadHook - deleted entry but it keeps returning upon
each PC bootup. Am I approaching this from the right direction? I am
unfamiliar with registry searching, would be grateful if you could run
me through correct procedures. To compensate for my ignorance in this I
downloaded and ran a regsearch utility (freeware) but access to
registry entries is "denied - unauthorised", is there some way of
getting around this?
Disabled/stopped services.msc NVIDIA Driver Helper Service
(C:|WINDOWS\System32\nvsvc32.exe) the only reference I could find to
NVIDEA. No apparent change to display characteristics after rebooting,
so I went into Device Manager and disabled Display adapters\NVIDEA
GeForce MX440 (all drivers), then custom configured display
characteristics to suit personal taste after re-booting.
I am anxious to streamline my OS as much as possible as I regularly
capture large MPEG video files (2GB - 6GB) and am having problems (more
about that in another thread PLEASE STAY TUNED) thus I would like to
disable all unnecessary resource consuming applications that I can. Hope
I'm not stretching the friendship in asking that you pass an opinion on
the way I am doing (or more likely "not doing") it. Many Thanks.
--
Bob Deb
:
Hi Bob,
(Default) REG_SZ (value not set) gets created whenever a new key
is created. Ignore these.
Sometimes when the (value not set) is missing there can be problems.
I am not sure exactly what happened, but glad you got rid of
WkDetect.exe.
Here's the skinny on NVIEW. I also have an Nvidia graphics card. I
have every Nvidia item that I can disabled, even the Nvidia right click
context menu stuff. If you want I can post all of that later.
Nview.dll = NVIDIA nView Desktop and Window Manager
Name NVIEW
Command rundll32.exe nview.dll, nViewLoadHook
Description This is a DLL to enable multiple display monitors on a
single computer. It can be a cause of numerous problems on some
computers
If you do not have multiple monitors, you can get rid of this.
Navigate to it in the registry...
NVIEW REG_SZ rundll32.exe nviewdll,nviewLoadHook
Then right click on NVIEW and select Delete, click YES to the prompt.
Also...
nvsvc32.exe is the NVIDIA Display Driver Service.
My advice...Disable it, it doesn't need to run. I have had mine
disabled for ages.
Disable the NVIDIA Display Driver Service...
Start | Run | Type: services.msc | OK |
Scroll down to and double click: NVIDIA Display Driver Service |
Under Startup type set to Disabled | Apply | Click the Stop button |
When it stops click OK | You may have to reboot
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In Bob Deb <
[email protected]> hunted and pecked:
Have solved the problem - neither Startup Insp or Reg Mech make any
reference to the missing Wkdetect.exe file but, being unfamiliar with
deleting reg entries, I am a little unsure about the procedure I used
being the correct way to do it. Could you please pass an opinion on
what happened:- Ran 'Regedit', Located and opened folder
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run Two
icons displayed: Name Type Data
(Default) REG_SZ -
NVIEW REG_SZ rundll32.exe
nviewdll,nviewLoadHook
I "double-clicked" the (Default) icon and an "Edit String" dialog box
opened, entered the Value Data (Value Name field dimmed out) and
"OK'd". This is where the unexpected happened, I expected to see
references to Wkdetect.exe in order that I could delete them but all
that happened was the Value Data was added to (Default) icon line:
Name Type Data
(Default) REG_SZ C:\Program Files\Microsoft
Works\WkDetect.exe
NVIEW REG_SZ rundll32.exe
nviewdll,nviewLoadHook Thinking "that's not what I'm after", I
immediately re-opened the dialog box and deleted the Value Data
string so that things were restored to normal, closed regedit and
restarted the PC. Problem fixed! No reference to Wkdetect.exe by
either utility. I have since done several restarts to ensure that it
is a continuing fix and not just a "one-off" fluke. But the method
does not seem right to me - it is certainly not what I anticipated,
did I go off the rails somewhere with my procedure? Look forward to
any advice you can offer. Many Thanks.
--
Bob Deb
:
Hi Bob,
may have reached its' "use by" date
LOL I like that!
Startup Inspector & Reg Mechanic are probably seeing a reference to
Wkdetect.exe, since it/they are pointing to a non-existent file both
complain.
Do a Registry search for Wkdetect.exe and get rid of any startup
references to Wkdetect.exe. Then you can get rid of the complaints.
From my research on the web, it supposedly starts from here...
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Value Name: Microsoft Works Update Detection
Value Data: C:\Program Files\Microsoft Works\WkDetect.exe
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In Bob Deb <
[email protected]> hunted and pecked:
Many Thanks for the advice, I have a theory (doubtless wrong) that
Works 6 may have reached its' "use by" date as far as future updates
are concerned, thus wkdetect.exe would be totally superfluous
anyway. Will have to give myself a slap on the wrist - forward
slashes instead of backslashes in my directory tree. I've been away
from DOS too long (more's the pity). Many thanks for you help, I
will keep ignoring the highlights from Startup Inspector and Reg
Mechanic. --
Bob Deb
:
Microsoft Works Update Detection
Wkdetect.exe checks for updates to MS Works
I have MS Works Suite 2004 (Works 7) and I do not have
Wkdetect.exe.
I have no idea what versions Wkdetect.exe came with. MS Works 6.0
for one, which is apparently the version that you have. ;-)
I would not worry about it. Just something that would be running
all of the time anyway.
You can check for updates here...
http://www.microsoft.com/products/works/downloads.mspx
The only update for Works 6 is that I saw was Works 6.0 Converter.
Only good if you have MS Word (included with the Suites). And
Works 6 Utility: Print Works Calendar.
It Starts from here...
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
As Microsoft Works Update Detection
C:\Program Files\Microsoft Works\WkDetect.exe
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In Bob Deb <
[email protected]> hunted and pecked:
Hi All,
Both my Startup Inspector and Registry Mechanic
continually highlight the fact that this file is non existant on
my XP OS. I have tried searching Microsoft.com for it but without
any real success. I have established it is to enable Works Update
Detection (I have MS Works 2002 Installed). Is it necessary to
have this file? If so, where on the net can I get to download it?
Many Thanks --
Bob Deb
