Newsletter Archives
-
Patch Lady – 1803 issues with peer to peer
A new “known issue” note was posted in the answers forum:
File Explorer may not detect other devices or perform file sharing on the local network when running Windows 10 version 1803
Justin posts:
Microsoft is aware of reports that devices running Windows 10 version 1803 cannot connect to other devices on their home network and is investigating the issue.
You can resolve this problem by setting some services to Automatic (Delayed Start) and restarting Windows:
- Press the Windows Key and R at the same time to bring up the Run dialog.
- Type services.msc in the Run dialog and press Enter.
- For each of the following services, locate the service in list, right-click the service and select Properties. Then set the Startup type to Automatic (Delayed Start) and select Apply.
- Computer Browser (Browser)
- Function Discovery Provider Host (FDPHost)
- Function Discovery Resource Publication (FDResPub)
- Network Connections (NetMan)
- UPnP Device Host (UPnPHost)
- Peer Name Resolution Protocol (PNRPSvc)
- Peer Networking Grouping (P2PSvc)
- Peer Networking Identity Manager (P2PIMSvc)
- Restart Windows.
-
Avast says Microsoft to blame for the Win10 1803 upgrade bluescreens and non-sensical boot loop options
Avast has released a new version of their antivirus software and, in a carefully worded explanation, take a jab at Microsoft’s botched Win10 1803 installer.
Computerworld Woody on Windows.
-
Patch Lady – 1803 getting offered up to Semi Annual
I have personally seen several credible reports of 1803 being offered up to folks that have Windows 10 pro, and have the updating deferral set to the Semi-annual channel. (here’s one visual example here)
Given that 1803 is not deemed to be semi-annual – it’s semi-annual targeted right now (what used to be called current branch) there is -zero- reason that it should be offered up on machine that have the deferral selected.
I’ve lost count how many time that the deferral process has not held.
I also remember that I said here that I was going to give Microsoft one more time to get it right. <big sigh>
Just the other day on the Microsoft “ask me anything”, someone asked what was Microsoft going to do to bring back trust in patching. Well respecting deferrals would go a long way to start bringing back the trust.
Computerworld Woody on Windows.
-
Patch Lady – Black screen issue acknowledged
UPDATE: Avast admits it’s them: https://forum.avast.com/index.php?topic=219218.15
The recent 1803 upgrading issue whereby you end up with a black screen and a big headache has now been acknowledged by Microsoft:
The leading theory right now is that third party antivirus is to blame
but the Register has spoken with Avast and they are saying it’s not the root cause. Bottom line we’re still in the dark as to the true root cause at this time.I still say:
- You should be on Pro not Home to defer feature updates
- If you are on Home you need to uninstall any third party antivirus and stay with Defender. If I had a dime for everytime I saw an issue where antivirus interfered with updates I would be an EXTREMELY rich woman right now. I know that folks like something third party to monitor what is happening to their systems, but these days with phishing, antivirus no longer is as effective as it once was, it brings risk of attacks (I can point to many an enterprise attack that used antivirus vulnerabilities to gain a toe-hold into the systems), and most importantly in times of upgrades, antivirus that is deep into the kernel often causes major issues.
-
Microsoft may be dodging coerced Win10 1803 upgrades on machines running Avast
Although the proclamation doesn’t come from official sources, a mod on the Avast forum says MS has stopped 1803 upgrades on machines running Avast antivirus.
Which may be a good reason to install Avast, eh?
Computerworld Woody on Windows.
-
Here’s a list of the major known bugs in Win10 version 1803
Note that I didn’t say “short list.”
Computerworld Woody on Windows.