Error: Access to specified device, path or file is denied

  • Thread starter Thread starter gab
  • Start date Start date
G

gab

Error: Access to specified device, path or file is denied

This has happened to me Twice on 2 differnt workstations.
No one nor Microsoft has been able to give an answer to
this situation.
Workstation runs Windows 2000 SP 3 or 4.
After turning on the computer, there are serveral Broken
links on Desktop and Folders.
Also We can't run any Executable. Not even Regedit, Dos,
or an MSI file. If we can get our executale files working
again we will be able somewhat solve the problem.
Can not install or uninstall. No viruses or worms found.

HELP HELP HELP
Email me at (e-mail address removed)
 
gab wrote in
Error: Access to specified device, path or file is denied

This has happened to me Twice on 2 differnt workstations.
No one nor Microsoft has been able to give an answer to
this situation.
Workstation runs Windows 2000 SP 3 or 4.
After turning on the computer, there are serveral Broken
links on Desktop and Folders.
Also We can't run any Executable. Not even Regedit, Dos,
or an MSI file. If we can get our executale files working
again we will be able somewhat solve the problem.
Can not install or uninstall. No viruses or worms found.
Click to expand...

Sounds somewhat like a PATH issue perhaps. Check the System
Environment PATH statement for inclusion of
%systemroot%\system32; (and others)
and confirm that the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
\Environment\
PATH=
is a REG_EXPAND_SZ Type

Mine starts with
"%SYSTEMROOT%\SYSTEM32;%SYSTEMROOT%;%SYSTEMROOT%\SYSTEM32\WBEM;"
 
Mark V wrote in
gab wrote in

Sounds somewhat like a PATH issue perhaps. Check the System
Environment PATH statement for inclusion of
%systemroot%\system32; (and others)
and confirm that the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
\Environment\
PATH=
is a REG_EXPAND_SZ Type

Mine starts with
"%SYSTEMROOT%\SYSTEM32;%SYSTEMROOT%;%SYSTEMROOT%\SYSTEM32\WBEM;"
Click to expand...

On second thought it sounds more like a file permissions issue
(ACLs). Or even a Group Policy setting. I guess not knowing more
has me guessing...
 
Back
Top