Share via

Microsoft Updates KB4481480, KB4480970, KB890830, Issues with Remote Desktop and Remote Access

Anonymous
2019-01-09T17:26:58+00:00

I have a computer running windows 7.

the computer updated Jan 9, 2019 at 3 am. updates were KB4481480, KB4480970 and KB890830.

this is a shared computer on our network. with at least 5 different users using the files and folders. mostly network drives. For administration we use Remote Desktop.

when I arrived to work I was informed no one could access the network shares on this computer. Remote desktop was not working either.  I could ping the computer from my PC. Even after a reboot, and resetting passwords we still had remote connection issues.

An authentication error has occurred.

The Local Security Authority cannot be contacted

Remote computer xxx.xxx.xx.xxx

this could be due to an expired password

Please update your password if it has expired

for assistance contact your administrator or technical support.

I could not find any solution to this issue.  I performed a restore to a point before the updates were installed.

after the restore users could again connect to the remote computer.

is there a solution to this issue? anyone else have remote connection issues after installing this update on a windows 7 machine?

Thank You

George

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

19 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-10T21:35:43+00:00

    This is what finally worked for me.

    An analysis of the issue was published on the German admin website Administrator.de. The analysis confirms the network share issue and that it is caused by the installation of KB4480960 or KB4480970.

    The issue is triggered only if the user attempting to make the connection is an administrator on the machine that hosts the Share. If the user is "just" a user on the device that hosts the share, the connection should be fine.

    A workaround has been published to address the issue. It modifies the Windows Registry and should be run on the system that hosts the share. Note that you need to run from an elevated command prompt.

    • reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
    • Reboot the PC.

    The Registry entry defines how administrator credentials are applied for remote access. A value of 1 sets the restrictions to Audit mode.

    Removal of the updates resolve the issue as well but will remove the security patches on the target system that Microsoft released in January 2019.

    I used the reg add. after I rebooted the computer I was able to use remote desktop and connect remotely to the network shares.  I hope this can help someone else.

    George Guel

    50+ people found this answer helpful.
    0 comments
  2. Anonymous
    2019-01-09T21:47:16+00:00

    uninstalling only KB4480970 fixed the issue for me on 3 machines

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2019-01-11T04:31:03+00:00

    Had problems accessing / viewing Win 7 Computer on network (from Administrator accounts) after windows update kb4480970 

    The following worked for and was a god send after going around the twist for a couple of hours.

    (Huge Thanks to George Guel)

    run from an elevated command prompt (run as Administrator).

    • reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
    • Reboot the PC.

    8 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-01-10T21:16:10+00:00

    I had a problem with LAN access of shared folders on my Win7 Pro system.  After much annoying time I gave up and uninstalled the security update kb4480970 that came last night.  This totally fixed my problem.  I then hidden the kb4480970 update.  I've yet to see anything from MS about this.

    Jack

    7 people found this answer helpful.
    0 comments