Windows 10: Cannot Access Mapped Drives or Domain after 1903 update

I have 2 computers - Dell Optiplex 7050 - that after the install and update of Windows 10 Pro feature 1903 can no longer access any mapped drives. These drives were mapped prior to the automatic update. When the update completes, they cannot be connected to and cannot create any new mapped drives.


It looks like it has something to some services not starting. The "Workstation" service is not running even though it is set to Automatic. When I try to start it I get an error code of 1068. I also cannot see anything on the domain I am supposed to be connected to.


Anyone else have this type of issue? It is only with this model of computer. Other computers updated and there was no problem.

:)

 

How can I get this mapped drive to reauthenticat at login

I'm trying to get this mapped drive on an xp machine to reauthenticate when the computer reboots or is logged back in. The account the user uses is on a domain that is currently unavailable (server failure). The physical drive being mapped is on the other server which has the other domain here.

Now i can login as another user i create on the domain, check reconnect at login no problem. But the next day files won't open unless she clicks the drive and enters the user password there. its not a big intervention, but id like it to be seemless.

Suggestions?

 

Unable to Map a Network Drive in Windows 10

Hi

• When did the issue start? -- We have updated OS from 7 to 10.
• Are you having an issue mapping a network drive, accessing the network drive, or both? -- Both
• Are your computers or drives connected to a domain? -- Yes

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.