|
There are isolated problems with current patches, but they are well-known and documented on this site. |
I’ll be updating this post with trending 1803 install issues I see and potential resolutions: I will note when an issue is expected and when (to the b
[See the full post at: Patch Lady – early trending issues with 1803]
Susan Bradley Patch Lady/Prudent patcher
not everyone will be getting the 1803 update even when checking at windows update. depends on what kind of hardware being used for Win10.
You only get it if your machine is deemed ready. If it’s not popping up, that’s a sign it’s not ready to go.
Susan Bradley Patch Lady/Prudent patcher
MS, in it’s hurry to get 1803 out there before it was 2 months late (instead of just one) and the name was wrong, dropped the Insider Preview 17134.1 on the public.
Why are you surprised? Now they have several million more Beta testers!!!
Exactly the same issue as posted on reddit. Maybe you can reproduce yourself. Fire up ISE, type Get- and the drop-down window won’t show up. Instead, you’ll notice a dot below. If you now press CTRL-SPACE to open the drop-down list, ISE will crash. If you check the event viewer, you may get the following exception details:
Application: PowerShell_ISE.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.VisualStudio.Language.Intellisense.Implementation.DefaultCompletionSessionPresenter.Microsoft.VisualStudio.Language.Intellisense.IPopupIntellisensePresenter.set_Opacity(Double)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.IntellisenseSessionStack.SetPresenterOpacity(Double)
at Microsoft.VisualStudio.Language.Intellisense.Implementation.IntellisenseSessionStack+<>c__DisplayClass18_0.b__0(System.Object, System.EventArgs)
at System.Windows.Threading.DispatcherTimer.FireTick(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at Microsoft.Windows.PowerShell.Gui.Internal.Program.ShowMainWindow(System.Collections.Generic.List1, Boolean, Boolean, System.Threading.SendOrPostCallback)
Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Reflection.RuntimeMethodInfo.Invoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
at Microsoft.Windows.PowerShell.GuiExe.Internal.GPowerShell.Main(System.String[])
`
Another related report at https://social.technet.microsoft.com/Forums/windowsserver/en-US/47ded9fb-0501-4953-92cc-ef55dbf86fbe/powershell-ise-where-are-the-default-snippets-after-win10-upgrade?forum=winserverpowershell
Tony,
Interesting. I haven’t noticed any change in my drive designations.
Tony,
Still seems to be ok here at least.
Issues here:
As predicted, Edge is now handling some links, rather than the default browser.
Search Indexing running constantly without much progress, disabled it.
taskbar search now includes web results, now way to stop it.
I normally use Win7 for anything productive that needs to happen on Windows, so I am considering replacing win10 with one or two linux distros..
I am using mbr disk, so i can only have four partitions, unless i want to go through a complete reinstall to use gpt.
You can stop by adding
0.0.0.0 www.bing.com
to the hosts file. Of course, you’ll have to live without Bing..
Microsoft admins: Here are all the features you’re losing in the Windows 10 April 2018 Update
Microsoft’s big April Update is here, and a number of Windows features have been removed or are having development ceased. Here’s the full list.
By Brandon Vigliarolo | May 1, 2018
The Windows 10 April 2018 Update, formerly known as the Spring Creators Update, is now available for download, and users will find a lot of new features—and some that are missing.
…
Microsoft has removed several Windows features from its latest release, version 1803, and has ceased development on several others with potential plans to remove them later on.
Windows 10 users and administrators shouldn’t be too concerned, though: The features being removed and end-of-lifed are mostly outdated. But be sure to read the whole list: Some of them may still be relevant.
Windows features removed in version 1803
Microsoft said that apps and code that depend on these features won’t work in 1803. Anybody who still uses one of these features should hold off upgrading until a workaround can be found:
Read the full article here
I think tunneling was or is part of the IPv6 standard. Like prioritising IPv6 over IPv4 if there is dual-stack provided in the product.
Or like PCI Express having certain behaviour. Remember KB4099950? 🙂
Not all bad things in life should be attributed to Microsoft.
I tend to agree with you about SRP. I liked the feature and for simple implementation it is much easier to use when compared to AppLocker which is a much better implementation, but it comes with a certain learning curve.
FYI,
If you’re running Windows 8.1 or later, you can disable tunneling with PowerShell:
Set-Net6to4configuration -state disabled
Set-Netisatapconfiguration -state disabled
Set-NetTeredoConfiguration -type disabled
Or set registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
DisabledComponents REG_DWORD to 1.
I would rather set it to 255 (decimal) – disable completely and correctly IPv6
or
33 (decimal) – disable tunneling and prioritize IPv4
I don’t know if this is a bug or part of the standard, but even if the IPv4 stack is prioritized, DNS name resolution still tries IPv6 first which creates major problems sometimes.
The only way around this behaviour is to completely disable IPv6 by setting the value above to FF (hex) or 255 (decimal).
https://support.microsoft.com/en-au/help/929852/how-to-disable-ipv6-or-its-components-in-windows
Those Spectre mitigations everyone struggled over – they’re only for 1709, and have not been rolled into 1803. This suggestion on Twitter from @SimonZerafa:
Might be worth getting folks to check their Spectre patch status thought. The @SGgrc tool shows I’m no longer protected for Spectre and the 1709 patch doesn’t install on 1803 obviously 🙁
Inspectre reports my system is still fully protected after the upgrade as it was before the upgrade. Might be worth checking for another bios update if anyone runs into that.
Red Ruffnsore
For those having issues with a new logical drive (OEM or restore partition) after upgrade, I’ve published an article with workarounds
Windows 10 V1803 update creates a new OEM Partition
Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author
https://www.borncity.com/win/
To quote from the article:
Some people notice after upgrading to Windows 10 April Update, that there is a new partition (recovery partition with Windows PE). Due to the fact, that a drive letter is assigned, the logical drive will be shown in explorer. And Windows 10 starts with annoying notifications, that the disk is full.
I was not offered the 1803 upgrade but for some reason I *was* reoffered the 1709 upgrade (which I had previously hidden; I’m currently on 1703). Not too sure why, but I definitely have no plans on leaving this stable, comfy haven that is 1703 anytime soon.
This actually raises an interesting question – which we’ve never hit before.
In 1703 (which I use on my production machines) I’m set up to defer upgrades for 365 days.
Question: Does that mean I’ll see deferred upgrades to 1709 for 365 days? Or for 1803? What if I want to defer 1803 upgrades for 365 days?
It’s just one of many, many questions that haven’t been answered about the current Windows Update.
(I just checked and 1709 doesn’t show up on my 1703 machines. Nor does 1803.)
I think that as long as you have feature updates deferred for 365 days you may not see them in WU. I found that with quality updates at least. If I defer them, I don’t see them until I set the deferral down to 0. That is why I leave my quality updates set to 0, so I see them in WU, but set the Auto Update in GP to Enabled, 2 so they don’t get downloaded.
When I wanted to upgrade one of my 1703 to 1709, all I did was set feature updates to 0 and it showed up. Try setting the feature updates to 0 – you can stop it using mcbsys’s method then set it back to 365.
That happened here to @Irene, but she kept running “Search for Updates” which just presents the upgrade and starts it’s download. She was upgraded (by surprise) from 1703 to 1709, then went searching for Office updates in WU and got 1803 starting to download (even she was thinking of rolling back to 1703).
You have to use wushowhide to search for updates. If you use WU you get more than you bargain for.
I’ve done rollbacks with no problem. BUT, there is always the chance you can have one that doesn’t work. So you’ve got to make the decision to take the risk or not. You need to take a good look at 1709 and be sure everything is working as you expect. You don’t have a long time to decide – I think 10 days is max and the Windows.old folder may disappear.
Whatever you do, if you don’t want 1803 at this point, DO NOT use Windows Update to “Search for updates” (I’m sure you have been readint the latest posts). Use wushowhide to hide 1803 and be careful what’s in the queue before you update anything.
Keep us posted. And stay around for the latest on whet’s happening.
@Irene … Here’s a post that may be of help to you. It may seem a little overwhelming at first, but it’s not really after you get the “hang” of it. Of course, I can only speak for myself, but It’s the ONLY way I’ve ever been able to keep 1709 at bay. The trick is you must never allow Windows Update Service to run without it being on a Metered Internet connection.
Here’s my “system”:
https://www.askwoody.com/forums/topic/how-to-really-truly-block-the-pushed-upgrade-to-the-next-version-of-windows-10-version-1803/#post-188621
I used it to do last month’s updates and it worked flawlessly. Hope it helps you, too. Good Luck!
@Irene – No problem. I’m recovering from an eye operation myself, and have been very limited in time spent on my computers, so your reply today was good timing. 🙂
In answer to your questions:
1. I did some investigating on the WUMT Wrapper Script when it came up awhile back here in the Lounge. I haven’t tried it, but as far as I can determine, it’s just a script you run as Administrator in Command Prompt that starts Windows Update Service and runs WUMT in update search mode. After you finish using WUMT, you close it, and the script turns WUS off. I could never determine that it also sets WUS to metered and non-metered automagically, which is the reason I’ve never used it. If it doesn’t also handle the metered to non-metered Internet connection, I really don’t see any real benefit in using it. In fact, by having to open Command prompt, find, copy and paste the script it’d probably take more time than using Windows Update Blocker and WUMT manually, IMHO.
2. Yes. Windows Update Service has to be running in order to do any updating, even if you download the updates from the Microsoft Update Catalog and install them manually. Just make sure you set your Internet connection to metered before starting Windows Update Service in order to install the updates/upgrades.
3. Yes, if you are using WUMT you don’t need to go to the Microsoft Update Catalog. I just set WUMT to “Microsoft Update” and it does it’s thing. I think that’s the default setting.
But, as previously stated, it’s been my experience that the big monthly Cumulative Update installs more quickly and more reliably by downloading it from the Microsoft Update Catalog and installing it manually. Others who know much more than I about these things might disagree, so take that with a grain of salt. 🙂
Also, just so things don’t get too simple with this WaaS updating/upgrading train wreck, you should know that WUMT actually only “hides” updates from the user, NOT from Windows Update Service. For that, you need to, use the WUShowHide tool, as Woody describes in detail in several places, including his ComputerWorld column. I use it as another brick wall MS would have to break through to force feed me an upgrade to the latest and greatest WIN 10 version that I don’t want right now.
Hope this helps and, as usual, Good Luck! Let me know if I might can help further, but we may need to consider taking our conversation to the Direct Messenger so Woody and the folks here won’t have to keep wading through these long comments … 🙂
Direct Message is a button at the top of the blog page nest to “Log Out”
Firefox has a bug with 1803 that is fixed with the 59.0.3 release that came out a couple of days ago. Release notes are here:
In Windows 10, by clicking Check for updates, this triggers download and install.
The only way to trigger a check without updating if the Group Policy is right was to run usoclient startscan
This is the same command run by the equivalent built-in Scheduled Task(s).
In the current latest Windows 1803 version 17134.5 (patched with non-public but official Microsoft KB4135051, which updates the version from 17134.1 to 17134.5) the command mentioned above does not run correctly. It behaves like checking if the time for running has come and stops running if it is too early, like running manually. No error is generated.
Windows Update still runs on its own schedule, but more consistently at log in as it seems.
This may be just an early bug which will be fixed at some stage in a future CU.
Other versions of Windows 10 had various bugs related to WU, most notably Windows Server 2016 (possible Windows 10 1607 LTSB at the same time) which was fixed only few months later by a CU.
Same behaviour was observed with the pre-release, “almost RTM” 17133.1 and 17133.73.
With Home, you have metered connections and wushowhide.
Unless you pay the $99.99 US to upgrade to Pro – well worth it.
Absolutely agree. Although I personally would chough up the hundred bucks per computer to get Pro, maybe some folks, like my wife and I, with three or four computers all coming with Home, don’t have $300 or $400 laying around to send off to Microsoft in order to control their forced-fed, unwanted updates and upgrades.
OTOH, there are rather complicated and time-consuming ways to do it, even with Home, but that shouldn’t be necessary. The vast, vast majority of users, like my wife, just want to turn the dang computer on, get her work (and play) done, turn the computer off and get on with life, and, indeed, “have a reasonable expectation that Microsoft won’t crash their machines.”
Sorry, you made your own luck if you are on Home, because you don’t care about maintaining the system like a Pro. Home editions are not supposed to be managed by end-users and everything that is posted here about home users managing their product is just a surrogate and not proper management.
I’m sorry, but I actually have to dispute this. Prior to Win 10, my personal computer was running Win 7 Home Premium. I hadn’t upgraded it to Pro for multiple reasons, in part financial (considering that during some of this time frame I was working two jobs and was the sole person working in the house I was living in…) and in part because I did not require the additional features at that time to properly manage my personal computer. In my current job, I was asked to be liason with our IT department when I got promoted into my current department, because even in my old department I was already the in-house tech support and IT knew my technical background (former professional tech support with a now sadly outdated programming background), and assisting people with technology is a major part of my job on a daily basis. So, I am reasonably knowledgeable.
When Win 10 came out, and I saw how upgrades were going to work, since by then my situation had changed, I was going to pony up the money and pay for the up-license to Pro from Home not only my computer, but also my housemate’s, since I’m the in-house admin. I waited until the very end of the free upgrade period to pull the trigger, though, and by that time, how Microsoft had already started neutering Pro was disgusting me. Pro was originally meant for small businesses, yet it feels like Microsoft forgets that a small business is still a business, and needs to do work, and slowly takes away more of the control that small business users need. $200 (rounded up) is chump change to Microsoft, but they lost that sale. I stayed on Home, as I refuse to give them my money, and I had seen that there were, and still are ways for users manage patching assuming that the users are responsible enough to a) do their research (both on methods to block patches and also on any issues with patches), b) practice safe computing, and c) install applicable patches when deemed safe to do so.
Even on 7 and earlier versions, before GWX made me wary of installing everything, I always read what each offered patch did and looked up any known issues and waited a few days before installing everything, because I knew better – I had done tech support, I had actually supported a product that Microsoft patches broke way back in the day (iirc it was Encarta 98, breaking non-MS products because of Visual C DLL changes until MS finally put out a Visual C patch). So, while I am aware that this is probably Microsoft’s stance on it (which, thinking about it, makes no sense as the default was automatic patching before – which should also make people pause, as it should have been only the educated users who deliberately were piecemeal patched before because they wanted control – food for thought for everyone), and I am aware that you aren’t a Microsoft shill, please do not say that Win 10 Home users do not care about maintaining their system the same way as Pro users. As shown here by multiple users, there are those that do, and presumably each one has their own reasons for being on Home instead of Pro.
We have a report that Office 2013 won’t install on an 1803 machine.
No problems installing Office 2013 pro plus on a clean install of 1803.
Red Ruffnsore
1) Left Click disabled on Start Menu and any MS core applications on the Taskbar including Skype, Action Center, Defender, Date/Time and Internet Explorer.
2) Right Click disabled on any and all opened Taskbar program icons but not Start Menu, Defender, Date/Time and Action Center.
3) Right Click Menu would pop up on Start Menu, Defender and Action Center. Only Start Menu options were functioning though. Defender window would open then immediately close. Nothing happened when selecting anything in Action Center menu.
4) Anything that required UAC to execute failed to open any interactive window or installation process.
Rolling back update remedied every issue. MS support explained the issue was not with changes made in their mandatory update but with hardware/outdated drivers that worked perfectly fine with 1709 yesterday.
Günter Born has a lengthy list.
Is this an Insider bug bash being carried out by the unsuspecting public?
Evidently there is an issue in x86 versions of 1803 that will cause System Image backups to fail with RPC errors. This also apparently causes issues with recovery from image and 1803 system repair discs.
This apparently doesn’t affect x64 installations. See This TenForums Thread for discussion.
I have personally replicated this on two 32-bit PC’s but have not tried the workaround involving 1709 wbengine.exe replacement. MS is supposedly aware of the issue.
Since MS officially announced last year that System Image Backup was deprecated, maybe they’re using the 1803 32-bit installations as the first tease for eventual removal. I’m betting this issue is a “feature” not a “bug.” And a contagious feature at that!
“Deprecated” means it’s still there, but not being developed anymore…
A few hours after I installed 1803, I wrote and published a short article about my first impressions, about which I’ve seen no mention elsewhere. Redstone Reverted describes two unwelcome changes.
David A. Gray
Designing for the Ages, One Challenge at a Time
Found interesting topic on Reddit with discussion of new mess of Windows 10 April Update which Removes “Shutdown” without updating.
https://www.reddit.com/r/Windows10/comments/8iizw4/windows_10_april_update_removes_shutdown_without/
Thanks for your reply columbia2011. I have run virtual machines on this PC in the past using VirtualBox. I find it curious that the 1803 update is blocked due to VT-d on some machines. The problem seems reasonably widespread if you search “Windows 1803 update VT-d”.
Here is a reddit thread for example:
https://www.reddit.com/r/windows/comments/8hiqnf/psa_disable_vtd_in_your_bios_if_windows_1803/
I am not in a hurry to upgrade. I was posting here more to inform others. I’ll wait and see if Microsoft provides a fix before I start fiddling around with the BIOS.
This is turning out to be a busy week for me. But I’ve come to the conclusion from a corporate perspective I’m tired of having to battle all these issues with all these different versions of Windows 10 and having to keep track of separate related issues. I have other things to do besides keeping track and wrestling with all these variables.
So Microsoft says 1803 is good to go. In that case I’m going to update all systems to 1803 in the next few weeks. The majority of our systems are running 1703 with some on 1709 and myself and a co worker are running 1803. I guess 1703 will be losing support soon enough and I’m not putting 1703 users through 2 version updates. So everyone will be going to 1803 in the next few weeks.
Maybe this is what Microsoft wants. I’m tired of battling this issue and other changes regarding Microsoft’s direction. I will continue to take precautions with updates and such but I want to establish some standards and common denominators to work with.
Regarding all this AI nonsense, I’m not even going to bothering fighting this issue. Microsoft may change their approach to things and I can do so as well. They want more control? Fine go for it. I shouldn’t have to wrestle with Microsoft’s changes constantly and I’m not dedicating my time and stress level to this on a daily basis.
Of course I’ll always follow Askwoody’s advise and there will still be a wait period on new updates. But I’m not creating more work for myself. Let Microsoft do their thing and let corporate heads decide whether to keep using Microsoft’s software.
Red Ruffnsore
2018-06 and 2018-07 cumulative updates for 1803 feature update did nothing to fix inability of certain motherboards to wake from task scheduler, so I have no choice but to restore three computers to pre-1803 and block future feature updates for those machines. I plan to use the WUMT Wrapper Script, which uses a combination of WUMT and WUB, that I’ve tested on another machine and works to still allow picking security updates while preventing forced updates. (The Asus AM2+ motherboards are about 5 years old and were a good choice to buy at the time, so I got the of them. The Windows as a service consequence of making hardware obsolete is working quite well, intentional or not.)
I cross-posted this here:
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
