201604 GJFPC2 Win 89.1 32bit drive failed

  • new drive restore from minimal system backup
  • Win 10 home upgrade
  • – sys back up -Win10-fresh
  • Chrome
  • Acrobat DC
  • Lexmark X363DN Universal Driver
  • Mapped M O S


So did this:

This is the effect of the User Account control (UAC) which was added in Windows Vista in 2006.When you map drives at logon, they are mapped with the filtered token (standard rights). When you now run an application elevated (with full admin token) it can’t see the mapped drives of the normal permissions.

When network shares are mapped, they are linked to the current logon session for the current process access token. This means that if a user uses the command prompt (cmd.exe) together with the filtered access token to map a network share, the network share is not mapped for processes that run with the full administrator access token.

To allow admin programs to see the normal mapped drives, enable the setting EnableLinkedConnections

Click Start, type regedit in the Start programs and files box, and then press ENTER.

Locate and then right-click the registry subkeyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Point to New, and then click DWORD Value.

Type EnableLinkedConnections, and then press ENTER.

Right-click EnableLinkedConnections, and then click Modify.

In the Value data box, type 1, and then click OK.

Exit Registry Editor, and then restart the computer.