After installing KB4480970 I cannot access shared folders or printers [duplicate]
This question already has an answer here:
What to do when a Windows Update (KB4480970) breaks your computer?
2 answers
I just installed KB4480970 on my Windows 7 computer LAB-PC. Now none of the other machines on my network can access the folders and printer I have shared from this computer.
Everything was working fine before the update. Turning off the Windows firewall didn't help. I can ping LAB-PC from other computers.
If I try to access my share "Test" on LAB-PC from another computer by typing \LAB-PCtest into Explorer's address bar, I get the error:
Windows cannot access \LAB-PCtest
I tried mapping a drive to LAB-PC by running net use Z: \LAB-PCtest and got the error:
System error 6 has occurred.
The handle is invalid.
I'm running Windows 7 Pro 64-bit. My computer is not in a domain. How can I fix this?
windows-7 networking network-shares
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
marked as duplicate by Ramhound, random♦ Jan 15 at 17:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
This question already has an answer here:
What to do when a Windows Update (KB4480970) breaks your computer?
2 answers
I just installed KB4480970 on my Windows 7 computer LAB-PC. Now none of the other machines on my network can access the folders and printer I have shared from this computer.
Everything was working fine before the update. Turning off the Windows firewall didn't help. I can ping LAB-PC from other computers.
If I try to access my share "Test" on LAB-PC from another computer by typing \LAB-PCtest into Explorer's address bar, I get the error:
Windows cannot access \LAB-PCtest
I tried mapping a drive to LAB-PC by running net use Z: \LAB-PCtest and got the error:
System error 6 has occurred.
The handle is invalid.
I'm running Windows 7 Pro 64-bit. My computer is not in a domain. How can I fix this?
windows-7 networking network-shares
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
marked as duplicate by Ramhound, random♦ Jan 15 at 17:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused byKB4480960andKB4480970and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.
– Ramhound
Jan 15 at 11:54
1
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago
add a comment |
This question already has an answer here:
What to do when a Windows Update (KB4480970) breaks your computer?
2 answers
I just installed KB4480970 on my Windows 7 computer LAB-PC. Now none of the other machines on my network can access the folders and printer I have shared from this computer.
Everything was working fine before the update. Turning off the Windows firewall didn't help. I can ping LAB-PC from other computers.
If I try to access my share "Test" on LAB-PC from another computer by typing \LAB-PCtest into Explorer's address bar, I get the error:
Windows cannot access \LAB-PCtest
I tried mapping a drive to LAB-PC by running net use Z: \LAB-PCtest and got the error:
System error 6 has occurred.
The handle is invalid.
I'm running Windows 7 Pro 64-bit. My computer is not in a domain. How can I fix this?
windows-7 networking network-shares
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
This question already has an answer here:
What to do when a Windows Update (KB4480970) breaks your computer?
2 answers
I just installed KB4480970 on my Windows 7 computer LAB-PC. Now none of the other machines on my network can access the folders and printer I have shared from this computer.
Everything was working fine before the update. Turning off the Windows firewall didn't help. I can ping LAB-PC from other computers.
If I try to access my share "Test" on LAB-PC from another computer by typing \LAB-PCtest into Explorer's address bar, I get the error:
Windows cannot access \LAB-PCtest
I tried mapping a drive to LAB-PC by running net use Z: \LAB-PCtest and got the error:
System error 6 has occurred.
The handle is invalid.
I'm running Windows 7 Pro 64-bit. My computer is not in a domain. How can I fix this?
This question already has an answer here:
What to do when a Windows Update (KB4480970) breaks your computer?
2 answers
windows-7 networking network-shares
windows-7 networking network-shares
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
edited Jan 15 at 0:43
Twisty Impersonator
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
asked Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
18.4k146699
marked as duplicate by Ramhound, random♦ Jan 15 at 17:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by Ramhound, random♦ Jan 15 at 17:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
2
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused byKB4480960andKB4480970and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.
– Ramhound
Jan 15 at 11:54
1
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago
add a comment |
2
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused byKB4480960andKB4480970and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.
– Ramhound
Jan 15 at 11:54
1
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago
2
2
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused by
KB4480960 and KB4480970 and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.– Ramhound
Jan 15 at 11:54
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused by
KB4480960 and KB4480970 and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.– Ramhound
Jan 15 at 11:54
1
1
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago
add a comment |
1 Answer
1
active
oldest
votes
This is a known issue caused by the January 8, 2019 Windows Update KB4480970. According to Microsoft this update introduces the following issue:
Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
On January 11 Microsoft released hotfix KB4487345 to resolve this issue:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
This hotfix is not being distributed via Windows Update. Instead, you must download it directly from the Microsoft Update Catalog website.
Install this hotfix on the computer hosting the network share(s) that users are not able to access. According to my testing it's not necessary to install it on computers from which one is trying to access the shared folders or printers.
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is a known issue caused by the January 8, 2019 Windows Update KB4480970. According to Microsoft this update introduces the following issue:
Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
On January 11 Microsoft released hotfix KB4487345 to resolve this issue:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
This hotfix is not being distributed via Windows Update. Instead, you must download it directly from the Microsoft Update Catalog website.
Install this hotfix on the computer hosting the network share(s) that users are not able to access. According to my testing it's not necessary to install it on computers from which one is trying to access the shared folders or printers.
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
add a comment |
This is a known issue caused by the January 8, 2019 Windows Update KB4480970. According to Microsoft this update introduces the following issue:
Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
On January 11 Microsoft released hotfix KB4487345 to resolve this issue:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
This hotfix is not being distributed via Windows Update. Instead, you must download it directly from the Microsoft Update Catalog website.
Install this hotfix on the computer hosting the network share(s) that users are not able to access. According to my testing it's not necessary to install it on computers from which one is trying to access the shared folders or printers.
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
add a comment |
This is a known issue caused by the January 8, 2019 Windows Update KB4480970. According to Microsoft this update introduces the following issue:
Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
On January 11 Microsoft released hotfix KB4487345 to resolve this issue:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
This hotfix is not being distributed via Windows Update. Instead, you must download it directly from the Microsoft Update Catalog website.
Install this hotfix on the computer hosting the network share(s) that users are not able to access. According to my testing it's not necessary to install it on computers from which one is trying to access the shared folders or printers.
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
This is a known issue caused by the January 8, 2019 Windows Update KB4480970. According to Microsoft this update introduces the following issue:
Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
On January 11 Microsoft released hotfix KB4487345 to resolve this issue:
This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows 7 SP1 and Windows Server 2008 R2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.
This hotfix is not being distributed via Windows Update. Instead, you must download it directly from the Microsoft Update Catalog website.
Install this hotfix on the computer hosting the network share(s) that users are not able to access. According to my testing it's not necessary to install it on computers from which one is trying to access the shared folders or printers.
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
edited Jan 15 at 0:34
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
answered Jan 15 at 0:26
Twisty ImpersonatorTwisty Impersonator
18.4k146699
18.4k146699
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
add a comment |
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
1
1
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
KB4480960 causes the network share problems also.
– Ramhound
Jan 15 at 2:52
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
ah for the love of dog. I've been fighting my PC for two days. Nearly re-installed all. Thanks for the post. Fixed it good in my case.
– MandoMando
Jan 31 at 17:00
add a comment |
2
The proposed duplicate is asking for general advice what to do when updates "like" this one break your computer. Quote: "...in general what should I do in these situations?" It does not describe the symptoms specific to this patch and is unlikely to be found by users searching for these problems.
– Twisty Impersonator
Jan 15 at 11:41
They are still connected and related, it's important to link, relevant issues to one another. The linked question was specifically about the issues caused by
KB4480960andKB4480970and honestly don't see anything generic about the linked question. By submitting the same answer to two questions you have caused an interesting issue.– Ramhound
Jan 15 at 11:54
1
I agree that proposed duplicate is general. found this one by searching for the specific "System error 6 has occurred". Otherwise I'd still be wrestling my pc and close to accepting defeat.
– MandoMando
Jan 31 at 17:08
This issue also causes authentication to fail with Visual Studio's Remote Debugger. Hotfix KB4487345 also fixes it.
– Nathan Kidd
3 hours ago