News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Patch Lady – early trending issues with 1803

    Posted on Susan Bradley Comment on the AskWoody Lounge

    Home Forums AskWoody blog Patch Lady – early trending issues with 1803

    Viewing 39 reply threads
    • Author
      Posts
      • #189360 Reply
        Susan Bradley
        Da Boss

        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

        5 users thanked author for this post.
      • #189366 Reply
        Mr. Natural
        AskWoody Plus

        I just finished upgrading my work pc. Windows 10 pro on a domain pushed via WSUS. Not seeing the drive letter issue. My laptop at home is an Alienware 17r3 but it’s running windows 10 pro so it isn’t seeing the 1803 update. (yes I manually ran windows update yesterday). I guess I’ll hold off on that a bit at home.

        My initial impression is it appears this version runs better than 1709. Things seem to load pretty quick. Event viewer looks pretty clean too compared to earlier versions. I did see that the system indexer gets reset due to an upgrade to the indexer.

        Thank you Susan!

        Red Ruffnsore

        • #189421 Reply
          EP
          AskWoody_MVP

          not everyone will be getting the 1803 update even when checking at windows update. depends on what kind of hardware being used for Win10.

          1 user thanked author for this post.
          • #189424 Reply
            Susan Bradley
            Da Boss

            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

            1 user thanked author for this post.
        • #189683 Reply
          Mr. Natural
          AskWoody Plus

          I ran the media creation tool (windows 10 pro) on my Alienware 17r3 last night and did not have any problems with the 1803 install. Sorry I don’t have the specs right now but can supply if interested.

          Red Ruffnsore

          • #189983 Reply
            Mr. Natural
            AskWoody Plus

            I would definitely follow Susan’s advise on any Alienware laptop despite my results. I was originally expecting to see an issue when I updated to see if I could troubleshoot the issue. I just happen to have the one model that does not appear to be affected. And you may have the same model as I, but if you have a different video card or who knows what other than what my system has you could wind up with a big mess.

            Red Ruffnsore

        • #189702 Reply
          ch100
          AskWoody_MVP

          I cannot say if it runs better than 1709, but it does not run worse.

      • #189392 Reply
        woody
        Da Boss

        From Martin Brinkmann at ghacks:

        • Start10 isn’t working
        • Users report that they can’t change the “feedback frequency” setting under Privacy > Diagnostics & feedback anymore. On my system, it states “Windows Insider Program manages this option” even though the PC never joined the program.
        • Right-clicks on programs in the Taskbar don’t display the context menu.

        Also note that 1803 includes .NET Framework 4.7.2. You can update your non-1803 computers to 4.7.2 if you feel so inclined.

        • #189396 Reply
          PKCano
          Da Boss

          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!!!

          4 users thanked author for this post.
          • #189432 Reply
            lurks about
            AskWoody Plus

            Beta testers? I thought they were alpha testers at this point </sarcasm>

            2 users thanked author for this post.
        • #189601 Reply
          djbaxter
          AskWoody Lounger

          Start10 is working just fine for me after upgrading to 1803 last night.

        • #189700 Reply
          ch100
          AskWoody_MVP

          There is a Group Policy for that.
          Because I had this set for ages to disable feedback, I didn’t even notice this new “feature” unless I read about it elsewhere.
          It was obviously an upgrade in place, in fact multiple upgrades.

      • #189443 Reply
        anonymous
        Guest

        PowerShell ISE is broken as well (https://www.reddit.com/r/PowerShell/comments/87n0l6/if_you_like_using_the_ise_you_might_want_to_hold/) and Microsoft doesn’t care to fix. What a bunch of critters.

        • #189476 Reply
          RetiredGeek
          AskWoody MVP

          The referenced article references “The latest insider build 17133”.

          I have had absolutely no problems with PS_ISE on builed17134 (1803).

          I’ve had to fix several programs to run under this version so I’ve given 1803 a pretty good work over in PS_ISE w/o problems.

          HTH 😎

          May the Forces of good computing be with you!

          RG

          PowerShell & VBA Rule!
          Computer Specs

          • #189580 Reply
            anonymous
            Guest

            It’s still broken in 1803 RTM on clean install. Maybe you can share what Windows features are enabled at your end? Thank you!

            • #189591 Reply
              woody
              Da Boss

              All of the entries on that Reddit thread are a month old.

              What problems are you encountering?

              • #189737 Reply
                anonymous
                Guest

                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.List

                1, 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[])
                `

                2 users thanked author for this post.
              • #189744 Reply
                anonymous
                Guest
        • #189697 Reply
          ch100
          AskWoody_MVP

          Not broken here.

          • #189738 Reply
            anonymous
            Guest

            You tried the ISE console?

          • #189739 Reply
            anonymous
            Guest

            Nevermind, the code window is affected as well.

      • #189454 Reply
        tonydi
        AskWoody Lounger

        Disk Management shows my boot drive (I have several drives in my PC) now as Drive 4 when it used to be Drive 0.  But if you look at the Properties for the drive, it shows Location 12 (Bus Number 0, Target Id 0, LUN 0).  None of the other drives show a Location number and  are simply labeled Bus Number 0, Target Id 2, LUN 0 – Bus Number 0, Target Id 3, LUN 0 – Bus Number 0, Target Id 4, LUN 0 – Bus Number 0, Target Id 5, LUN 0.

        So far I haven’t seen any ill effects over this change but it’s still early….

         

        • #189481 Reply
          RetiredGeek
          AskWoody MVP

          Tony,

          Interesting. I haven’t noticed any change in my drive designations.

          Disk Management Screen Shot Win 10 1803DiskMgmt1803

          May the Forces of good computing be with you!

          RG

          PowerShell & VBA Rule!
          Computer Specs

          Attachments:
          • #189488 Reply
            tonydi
            AskWoody Lounger

            I went into Disk Management to see if it had put back the Recovery partition and sure enough it had.  That’s when I noticed Disk 0 was now Disk 4.  My DM window looks just like yours.  But right click on the grey box to the left of your visual disk layout, where it says Disk 0, Basic, 223.45GB Online and select Properties.

            That’s where I noticed the new “Location” number.

            I know Win10 Updates have mucked with drive identifiers the past.  I use Macrium Reflect and set it to delete the oldest backup when the backup drive gets too full.  After some big updates Macrium doesn’t recognize the oldest backups as coming from the same drive so it leaves them alone.  Come to find out that Windows changed the drive identifier, for reasons unknown.

             

             

            • #189504 Reply
              RetiredGeek
              AskWoody MVP

              Tony,

              Still seems to be ok here at least.

              DiskMgmt1803props

              May the Forces of good computing be with you!

              RG

              PowerShell & VBA Rule!
              Computer Specs

              Attachments:
      • #189491 Reply
        anonymous
        Guest

        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.

        1 user thanked author for this post.
        • #189584 Reply
          anonymous
          Guest

          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..

          1 user thanked author for this post.
      • #189535 Reply
        Kirsty
        Da Boss

        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

        4 users thanked author for this post.
        • #189536 Reply
          AlexEiffel
          AskWoody_MVP

          I always disabled tunneling. It is an unnecessry security risk to me. Good riddance. Another example of a bad default set without thinking twice, putting no limits new features ahead of cautious changes that favor security. Like the wifi sharing password with your friends, which was overblown but still not such a great idea.

          SRP it makes sense but Applocker is only available on Enterprise, so another way to consumerize Pro.

          • #189579 Reply
            ch100
            AskWoody_MVP

            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.

            1 user thanked author for this post.
          • #189618 Reply
            RetiredGeek
            AskWoody MVP

            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

            May the Forces of good computing be with you!

            RG

            PowerShell & VBA Rule!
            Computer Specs

            1 user thanked author for this post.
            • #189691 Reply
              ch100
              AskWoody_MVP

              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

              1 user thanked author for this post.
      • #189592 Reply
        woody
        Da Boss

        Just saw this, linked from Bogdan Popa on Softpedia:

        Chrome freezes in April 2018 update.

         

        2 users thanked author for this post.
      • #189595 Reply
        woody
        Da Boss

        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 tool shows I’m no longer protected for Spectre and the 1709 patch doesn’t install on 1803 obviously 🙁

        2 users thanked author for this post.
        • #189616 Reply
          Mr. Natural
          AskWoody Plus

          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

          1 user thanked author for this post.
        • #189732 Reply
          EP
          AskWoody_MVP

          @woody & others:

          Microsoft has yet to confirm (or deny) as to whether or not the Meltdown/Spectre fixes are actually included in the 1803 update. so far, they haven’t said anything about it.

          also Microsoft security advisory ADV180002 has not been updated to mention about the 1803 update or whether MS will be making any Meltdown/Spectre patches for the 1803 release (maybe check back on patch Tuesday May 8 and see)

        • #189917 Reply
          anonymous
          Guest

          Here’s the result from the ‘Speculation Control Validation PowerShell Script’ after the upgrade from 1709 to 1803 (guest OS in Hyper-V):

          Speculation control settings for CVE-2017-5715 [branch target injection]
          For more information about the output below, please refer to https://support.microsoft.com/en-in/help/4074629
          
          Hardware support for branch target injection mitigation is present: True
          Windows OS support for branch target injection mitigation is present: True
          Windows OS support for branch target injection mitigation is enabled: True
          
          Speculation control settings for CVE-2017-5754 [rogue data cache load]
          
          Hardware requires kernel VA shadowing: True
          Windows OS support for kernel VA shadow is present: True
          Windows OS support for kernel VA shadow is enabled: True
          Windows OS support for PCID performance optimization is enabled: True [not required for security]
          
          BTIHardwarePresent : True
          BTIWindowsSupportPresent : True
          BTIWindowsSupportEnabled : True
          BTIDisabledBySystemPolicy : False
          BTIDisabledByNoHardwareSupport : False
          KVAShadowRequired : True
          KVAShadowWindowsSupportPresent : True
          KVAShadowWindowsSupportEnabled : True
          KVAShadowPcidEnabled : True
      • #189602 Reply
        djbaxter
        AskWoody Lounger

        Upgraded to 1803 yesterday evening.

        Sadly, 7+ Taskbar Tweaker is not working with this update. It pops up an error saying it can’t load a dll file and can’t integrate with File Explorer.

        I hope this is upgraded soon. I didn’t realize how much I had come to depend on this great little utility.

      • #189621 Reply
        Mr. Natural
        AskWoody Plus

        Just like every previous release, I’m having to reinstall RSAT. 🙁

        Red Ruffnsore

        • #189715 Reply
          Microfix
          AskWoody MVP

          RSAT available for new and previous versions of W10: Here

          No problem can be solved from the same level of consciousness that created IT - AE
        • #192261 Reply
          anonymous
          Guest

          Also reinstalling WADK

      • #189624 Reply
        jabeattyauditor
        AskWoody Lounger

        Just like every previous release, I’m having to reinstall RSAT. 🙂

        I don’t see a new version for 1803 either… but thanks for the heads-up, as I hadn’t noticed my tools were gone yet.

        • #190275 Reply
          anonymous
          Guest

          The version number in the RSAT tools filename refers to the version of Windows Server you are administering, NOT the version of Windows you are installing on.  There isn’t a 1803 version of Windows Server, yet.

      • #189636 Reply
        gborn
        AskWoody_MVP

        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

         

        Microsoft Windows Insider MVP, Microsoft Answers Community Moderator, Blogger, Book author

        https://www.borncity.com/win/

        5 users thanked author for this post.
        • #189640 Reply
          woody
          Da Boss

          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.

          2 users thanked author for this post.
        • #189696 Reply
          ch100
          AskWoody_MVP

          Try the upgrade with switches
          setup.exe /migchoice upgrade /dynamicupdate disable /resizerecoverypartition disable /showoobe full /telemetry disable
          or a variation of it as suitable.
          /resizerecoverypartition disable is the switch of interest here
          /migchoice is undocumented (thanks @abbodi86). The officially documented equivalent with less functionality is /auto

      • #189664 Reply
        anonymous
        Guest

        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.

        1 user thanked author for this post.
        • #189668 Reply
          woody
          Da Boss

          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.)

          1 user thanked author for this post.
          • #189670 Reply
            PKCano
            Da Boss

            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.

            1 user thanked author for this post.
            • #189694 Reply
              woody
              Da Boss

              I hope that’s the way it works for feature updates = version changes!

          • #189672 Reply
            Microfix
            AskWoody MVP

            MS have been scripting their own rules since the GWX campaign so, what’s to stop MS from upgrading v1709 and previous versions to the newest irritation iteration?

            I read somewhere (github, I think) that someone was on v1703 and they were also offered v1709 upgraded, then once done were upgraded to v1803 (last Monday v1803 was released via WU) It may have been coincidence but, with MS’s track record over the last few years..who knows?

            No problem can be solved from the same level of consciousness that created IT - AE
            • #189676 Reply
              PKCano
              Da Boss

              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.

              2 users thanked author for this post.
              • #189682 Reply
                Irene
                AskWoody Plus

                Just to add a bit of detail to that, I did search for the update in wushowhide, but you must apparently have to do it exactly as Mcbsys’s suggests or you will get hit.  It seems you must be on your toes, and not interrupted to do it Mcbsys’s method.

                I am contemplating rolling back to 1703, but I wonder if rolling back works 99% of the time.  If it has a relatively high failure rate, it may not be worth it, and if it is not then I’ll stay on 1709.

                Who knows what the statistics for successful roll backs are?   I’m just not in a mental place to try to do a system image replacement for the first time if it fails with all sorts of other stuff being thrown at me this week.

                Thanks for the answer ahead of time.

              • #189686 Reply
                PKCano
                Da Boss

                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.

                1 user thanked author for this post.
              • #189693 Reply
                Irene
                AskWoody Plus

                Thanks for the information.  Just to be clear though, I did hide 1709 twice.  Once on Sunday the 29th.  I searched for it on the 30th with wushowhide it was not there.  I checked my hidden updates/versions with wushowhide and 1709 was still hidden, so all seemed clear to go ahead with getting my MS Office updates, and within 2.5 or less minutes of checking it as hidden, 1709 started to download, so it isn’t as if I was being blind to the fact that they were pushing 1709.  That is why I say it has to be done just as Mcbys says, at least I hope it works for me if I decide to roll back, or if I stay on 1709 and I can avoid 1803 which also tried to come down the chute, and I checked the wusowhide directly before that too.

              • #189779 Reply
                dononline
                AskWoody Plus

                @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”:

                How to really, truly block the pushed upgrade to the next version of Windows 10, version 1803

                I used it to do last month’s updates and it worked flawlessly. Hope it helps you, too. Good Luck!

                1 user thanked author for this post.
              • #190229 Reply
                Irene
                AskWoody Plus

                @dononline Thanks for the tip.  I wasn’t even near a computer yesterday to see this, nor do I get the notices of replies to posts.  I am not sure why.  Woody’s site doesn’t like my VPN I guess.

                I read your post, earlier and noted it.  I am still on 1709.  I haven’t not used my Win 10 home since it happened.  I use my Mac most of the time now.  I do need to evaluate if all works on 1709, if it does, I may just stick with it.  I know I am running out of time to roll it back.

                Just to clarify, you unhide updates and/or versions of win 10 you want to install while on metered connection and then run the update tool, or one of the other two you mention.  When Windows update runs, while you are on metered, does it find the ones you unhid?  What happens if something like 1709 was hidden, as in my case when it snuck in via WU, and it ends up in the queue with things like MS Office updates?  My 1709 was hidden, it just pushed itself on me, and then tried to download 1803 so I immediately went off line and that stopped.  I have hidden 1803 since that time, but I don’t trust MS.

                You say your other two tools are just downloaded to a folder.  Does that mean they run from the folder and you do not have to install them?

                Thank you!

              • #190312 Reply
                dononline
                AskWoody Plus

                @Irene … You’re very welcome. Whether you decide to keep 1709 or roll back, I hope all goes well for you. If you stick with 1709, as you well know, 1803 will be trying to break through your defenses and install itself again, so you’ll probably want a way to keep that from happening at least until the many reported problems with it are hopefully ironed out over the next few months.

                Please note that what I posted is designed for using the Windows Update Blocker and Windows Update MiniTool. With these tools, you never have to even open Settings> Update & security> Windows Update> Check for updates. I’m assuming that’s what you were referring to when you said, “When Windows update runs …”, correct? If so, please note that all the updates are done with the WUMT while you are on Metered.

                WUMT just bores right on through the Metered connection and performs the installs, so at no time during the updating process is the Windows Update Service running without a Metered connection. As long as MS honors not forcing upgrades through Metered connections, 1709 and 1803 will not install. Maybe. I don’t trust MS either! 🙂

                After you launch WUMT and check for updates the first time, all available updates will be listed and the “Windows Update” button will be highlighted. It will probably be a long list, because it also includes drivers, most if not all of which are outdated, and some other stuff you don’t want or need. They’re all preceded by a check box, so just click to check all the ones you want to hide and click the +H (Show/Hide) icon. This of course would include the 1709 or 1803 Upgrades. You can “mouse over” all the icons for pop-ups telling you what each one is for. Other than that, the interface of WUMT clearly states what each “button” or “check box” is for. Just take a good look at the entire interface before using the tool to make sure the settings are like you want them.

                So then you’ll be left with only the updates/upgrades you want to download and install. You can see the ones you hid by clicking the “Hidden” button. From this point on, the “hidden” ones will remain “hidden” until you check them and click the +H (Show/Hide) icon to “unhide” them. You can go back and see the ones you want to install by clicking the “Windows Update” button. Here you simply click to check each one and then click the “Download and Install” icon.

                You could check them all and let WUMT do it’s thing, I suppose, but I don’t like that idea. I like to download and install them one at the time, starting with the Windows Malicious Software Removal Tool, followed by the Servicing stack updates, followed by the others, except for the Office updates. Those I download and install all at once. There are sometimes others that would make sense to group. It takes a little longer, but I just like to play it “safe”. I also like to download the Cumulative Updates from the Windows Update Catalog and manually install them. It seems faster that way. If you’re running an anti-virus or security suite other than Windows Defender, be sure to disable it before doing any updating.

                You are correct that neither WUMT or WUB requires installation. Just put them any place that makes sense to you and double-click the .exe file to launch. I made folders for them in the respective C:\Program Files folders. WUMT comes in x64 and x86. I use the x64 version. WUB is x86 only. Then I made shortcuts and pinned them to the Start Menu.

                I hope all this makes sense, Irene. If not, put the blame on me, and let me know if you have any questions. It’s really not as complicated as it might seem at first glance. We’ll get this thing up and running for you if you decide this is something you want to try. It took me about a month to get it figured out and everything put in place. The April updates were the first time I used this “system”, and by just taking it one step at the time, it went like a charm.

                If you’d rather use one of the other “systems” suggested here in the Lounge, just keep in mind that at no time do you want to have Windows Update Service running on a non-metered connection. I got “bitten” three times before figuring that out! 🙂

                Good Luck!

              • #195031 Reply
                Irene
                AskWoody Plus

                @Dononline – I’m a bit late at setting this up due to  unplanned life stuff, but I have a few questions if you would not mind answering them.

                1.  Is the Windows Update Mini Tool the same as the Windows Update Mini Tool Script Wrapper.  I was just checking some things out here on AskWoody and found discussions on the later.  The version numbers appear different, but I am too much of a “user” than a person knowledgeable in computers.

                2.  Do you have to enable or “allow updates” with the Windows Update Blocker to install from the catalog? (one keeps it on disabled when avoiding updates)

                3.  After one downloads the Windows Update Mini Tool, you hide all the updates you don’t want and then install the ones you do want using the update mini tool—but here is where my confusion is.  If you download directly from the catalog, does the Update Mini Tool take the updates for your machine from the catalogue, or am I mixing up two different things, i.e., if you are using the Update Mini Tool you do not need to go to the catalog?

                I hope you are able to find this because it’s been so long since you posted, and I do appreciate your time, or that of anyone else who can answer these questions for me.

                Thanks!

              • #195089 Reply
                dononline
                AskWoody Plus

                @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 … 🙂

                1 user thanked author for this post.
              • #195263 Reply
                Irene
                AskWoody Plus

                @Dononline  again, thank you!  I too went under the knife.  I will work on this tomorrow-6-1-18.  I have looked and do not see a messaging system “Direct Messenger” on Woody’s site, so I am not clear what you mean.  If I have further questions, I agree, that is the way to go.  I am just not sure how to go about that.

              • #195266 Reply
                PKCano
                Da Boss

                Direct Message is a button at the top of the blog page nest to “Log Out”

                3 users thanked author for this post.
              • #214498 Reply
                Mick Mickle
                AskWoody Plus

                 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. 

                @dononline – Where did you get the information that WUMT hides updates only from the user?  I think that if you investigate further, you’ll find that it truly hides the updates, at least until MS reincarnates them in new distributions, and then they may become unhidden just as they do when hidden with WUShowHide. Try this: Hide an update with WUShowHide, then run WUMT and you’ll see that hidden update is listed as hidden in that program.

                Note also that you’ve over simplified how the WUMT Wrapper Script works. In addition to running WUB to keep the Windows Update service disabled until you decide to update manually with WUMT then disabling the service again after closing WUMT, it also disables the numerous WU “facilitators” that MS keeps putting on our machines to force updates.  You’ll also find that when WUMT is running that Windows Update in Windows 10 Settings will not update on its own. Thus, the metered/unmetered setting is not needed. While running, the Wrapper Script also allows Windows Defender to update automatically if you are using it.

                WUMT Wrapper Script does a fine job of locking down several of my computers that have reached their limit with insidious feature updates.

                The Wrapper Script has been developed to a much higher degree than when you posted about it in May. I encourage you to revisit the MDL forum for it.  The script installs in your program start menu and is readily accessible like any program (pin to taskbar, etc.). So it’s a misconception that you have to open a command prompt and find the script to run. It’s more sophisticated than that.  In addition, another MDL project, Windows Update Manager (wumgr), is putting the WUMT functionality into an open source program, and that will probably be the core update program used by the Wrapper Script in the near future.

              • #214779 Reply
                dononline
                AskWoody Plus

                Thanks, Mick, for the info on the latest WUMT Wrapper Script. I’ll definitely check it out when I get back on my feet from current health problems.

                Frankly, I’ve just flat out forgotten where I got the idea that WUMT hides updates only from the user, and not from WUS also, as WUShowHide does. I DO recall that I had a couple of computers force-updated by WUS when the updates were hidden in WUMT, but not also in WUShowHide, though. More than once. I probably just deduced it from those experiences.

                I also like the Windows Update Manager Project you mentioned. I’ll follow the progress on that, too.

              • #190403 Reply
                dononline
                AskWoody Plus

                @Irene … After I went to bed last night, it dawned on me that, for the last couple of posts I’ve made on this subject, I’ve forgotten to add a very important caveat. That is, Woody does not recommend using the Windows Update MiniTool, nor keeping Windows Update Service turned off until needed, for very good reasons as he’s explained in his articles at Computer World and here in the Lounge.

                So, please consider this when deciding what tactics and tools you want to use to defend against MS’s forced upgrades and updates. Woody and many others here in the Lounge know far more about this stuff than I. I offer this only as something that I’ve found, after trying everything else I could find here and elsewhere that, so far, seems to work for me.

                Please read this:
                https://www.computerworld.com/article/3232632/microsoft-windows/how-to-block-windows-10-april-2018-update-from-installing.html

                Plus, as I’ve said before, MS could “fix” this “bug” in their new WaaS project at any time, rendering these tools and settings obsolete.

                Again, good luck with whichever path you decide to take.

      • #189681 Reply
        mobartz
        AskWoody Lounger

        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:

        https://www.mozilla.org/en-US/firefox/59.0.3/releasenotes/?utm_source=firefox-browser&utm_medium=firefox-browser&utm_campaign=whatsnew

         

        3 users thanked author for this post.
      • #189695 Reply
        ch100
        AskWoody_MVP

        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.

        2 users thanked author for this post.
        • #189701 Reply
          anonymous
          Guest

          But if you are on Windows 10 Home , then you are out of luck because you can’t change group policy.  Thus, Windows 10 Home people are just out of luck, correct?

          • #189710 Reply
            PKCano
            Da Boss

            With Home, you have metered connections and wushowhide.

            Unless you pay the $99.99 US to upgrade to Pro – well worth it.

            1 user thanked author for this post.
          • #189717 Reply
            ch100
            AskWoody_MVP

            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.

            • #189734 Reply
              EP
              AskWoody_MVP

              win10 home users could try using the WUMT Wrapper Script, which includes WUB (windows update blocker) and WUMT (windows update minitool).

              • #189778 Reply
                dononline
                AskWoody Plus

                Does the WUMT Wrapper Script also switch the Internet connection to Metered, so that Windows Update Service is never running on a non-Metered connection? It wasn’t clear to me that it does from the brief look I had at the directions.

                If not, it won’t keep 1709 at bay on any of my three computers.

                If so, I’d sure like to give it a look, as I’m manually doing all this with WUMT and WUB. I did last month’s updates with them and it worked flawlessly — but ONLY by never allowing Windows Update Service to run without being on a Metered Internet connection. A little automation would be nice!

                My “system” can be found here: #188621

            • #189751 Reply
              woody
              Da Boss

              Walllllllll. OK. I see what you’re saying.

              But Win10 Home customers don’t deserve to function as unpaid beta testers. They have a reasonable expectation that Microsoft won’t crash their machines.

              Agreed?

              3 users thanked author for this post.
              • #189754 Reply
                anonymous
                Guest

                I agree Woody! We home edition users are not lab rats!
                We are human beings!

                2 users thanked author for this post.
              • #189781 Reply
                dononline
                AskWoody Plus

                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.”

                1 user thanked author for this post.
            • #189771 Reply
              AlexEiffel
              AskWoody_MVP

              Ouch! Soon you will say the same about Pro version users vs Enterprise version as Ms keeps removing our ability to manage our own PCs.

              Not sure delaying unwanted updates should be seen as Pro only management of one’s own PC…

              2 users thanked author for this post.
            • #190302 Reply
              mindwarp
              AskWoody Lounger

              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.

              6 users thanked author for this post.
      • #189752 Reply
        woody
        Da Boss

        Proof of concept code published for crashing on all recent Windows versions (not just 1803).

        Catalin Cimpanu, Bleeping Computer.

        • #189923 Reply
          anonymous
          Guest

          Another reason to disable AutoPlay and think-first-before-clicking…

      • #189959 Reply
        woody
        Da Boss

        Yep, MS is acknowledging the Chrome freezing bug — with a surprising addition. Cortana.

        From the Answers forum:

        Some devices may hang or freeze when using certain apps, such as “Hey Cortana” or Chrome, after installing the Windows 10 April 2018 Update

         

      • #190013 Reply
        woody
        Da Boss

        We have a report that Office 2013 won’t install on an 1803 machine.

        Has the release of Windows 10 version 1803, due today, been delayed?

        1 user thanked author for this post.
        • #190115 Reply
          Mr. Natural
          AskWoody Plus

          I’m going to see if I can verify this. I have a Dell Latitude E5440 which I’m going to run the media creation tool and wipe the drive with a clean install. I have a copy of office 2013 pro open license version which I will try installing after the os is done.

          Red Ruffnsore

          • #190171 Reply
            Mr. Natural
            AskWoody Plus

            No problems installing Office 2013 pro plus on a clean install of 1803.

            Red Ruffnsore

            1 user thanked author for this post.
      • #190012 Reply
        Otkon
        AskWoody Lounger

        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.

        1 user thanked author for this post.
      • #190121 Reply
        woody
        Da Boss

        BSOD –  CRITICAL_PROCESS_DIED

        Seems to be associated with many Universal Windows apps.

        Reddit.

      • #190138 Reply
        woody
        Da Boss

        Günter Born has a lengthy list.

        2 users thanked author for this post.
      • #190145 Reply
        PKCano
        Da Boss

        Is this an Insider bug bash being carried out by the unsuspecting public?

        2 users thanked author for this post.
      • #190428 Reply
        anonymous
        Guest

        Isn’t the defer feature updates for X days supposed to make the feature updates (1709, 1803) not show up until they are X days old. So if you set it to 60 days it should show 1709 (older than 60 days) but not 1803 (younger than 60 days)?

        Is that how it is supposed to work? Is that how it does work?

      • #190452 Reply
        anonymous
        Guest

        Another one:

        Settings | Apps | Default apps | Set defaults per app: for 2 seconds nothing happened then it crashes out of the settings window.

        • #190706 Reply
          woody
          Da Boss

          Again?

          That was supposed to have been fixed in the beta….

      • #190608 Reply
        ch100
        AskWoody_MVP

        This is an older one, but still an issue in 1803.
        MiracastView package cause sysprep error after you upgrade a computer to Windows 10 Version 1709
        https://support.microsoft.com/en-us/help/4057974/miracastview-cause-sysprep-error-windows-10-version-1709
        I have an upgraded installation in place to 1803 from each version in sequence and MiracastView shows as installed under the regular user (which is me) and pending removal for the built-in Administrator (which was enabled manually) and used sometimes to browse through the file system without taking ownership under a different user.
        Get-AppxPackage -AllUser | Format-List -Property PackageFullName,PackageUserInformation
        The folder C:\Windows\MiracastView is missing which I think is expected from 1709 onwards, but to complete the migration for which the expected outcome seems to be to remove MiracastView from 1709/1803, I believe I will have to build an older version 1703, copy the files over and allow Windows to do its thing, which indicates a buggy setup sequence in this case.

      • #190682 Reply
        anonymous
        Guest

        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.

        1 user thanked author for this post.
        • #190707 Reply
          woody
          Da Boss
          • #190718 Reply
            anonymous
            Guest

            I sincerely hope Patch Tuesday fixes this.  The only way I maintain sanity sailing the seas of Windows 10 these days is with a disciplined backup routine!  And time is running out to revert via Windows.old…

          • #190782 Reply
            anonymous
            Guest

            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!

            1 user thanked author for this post.
            • #190784 Reply
              Microfix
              AskWoody MVP

              This article applies to the following:
              Windows 10 Fall Creators Update

              Did System Image Backup (SIB) work in W10 v1709 32bit or 64bit?

              or is it that no-one has noticed or missed it?

              No problem can be solved from the same level of consciousness that created IT - AE
              • #190842 Reply
                radosuaf
                AskWoody Lounger

                “Deprecated” means it’s still there, but not being developed anymore…

                MSI H110 PC MATE * Intel Core i5-6402P * 2 x 8 GB Corsair Vengeance LPX DDR4 2133 MHz * Aorus Radeon RX 570 4GB * Samsung 840 EVO 250GB SSD * Western Digital Blue 1TB HDD * Seagate Barracuda 1TB HDD * DVD RW Lite-ON iHAS 124 * Creative X-Fi XtremeGamer PCI * Windows 10 Pro 2004 64-bit
                1 user thanked author for this post.
              • #190845 Reply
                Microfix
                AskWoody MVP

                Yup my error 🙂

                No problem can be solved from the same level of consciousness that created IT - AE
              • #190844 Reply
                anonymous
                Guest

                It did work in 1709, both 32-bit and 64-bit.  Article is just indicating it is deprecated as of v1709.  Seems 1803 may provide the next logical step towards removal.

      • #190691 Reply
        SiriusBlack
        AskWoody Lounger

        Hi folks

        Just to add misery on the pile, I’ve tried, or rather W10 Pro has tried to Update to 1803 for the last 2 days and its only ended in stop code errors on the blue screen (oops something’s gone wrong) with me having a feeling of de ja vu from the last time.

        After reverting back to the old version 1709 (which it does itself), I have found issues with Chrome and a microsoft.com redirect web page malware which Norton stops only when if you remove the actual page that’s pinned that it doesn’t like.

        Current its telling me it want’s to have another go so I took Woody’s advice and deferred the update for 365 days however wushowhide is not showing the update to hide it, in fact its showing nothing.

        I’ve resorted to removing the WindowsUpgrade directory as well now.

        Just thought I’d share this

      • #190692 Reply
        SiriusBlack
        AskWoody Lounger

        Oh by the way after reverting back to 1709 it took 2 hours last night to get all the USB drives seen again for some unknown reason as they were fine before the upgrade attempt.

      • #190701 Reply
        anonymous
        Guest
        • #190837 Reply
          ch100
          AskWoody_MVP

          It was always a poor idea to redirect AppData\Roaming. Every other folder which can be redirected should be redirected and it is actually good practice where suitable, roaming profiles or not.
          I don’t know the details of the current issue, but if this is intended, I am all for it.

        • #190874 Reply
          PiqueABoo
          AskWoody Lounger

          Last week, for me, 1803 was ignoring the default folder exclusions when saving a roaming profile at log-off. As a consequence it got stuck at random places copying stuff under <profile>\AppData\Local and gave ‘could not save your profile’ messages.

          Solution was to add the default exclusions to my custom folder exclusions (via the GPO FolderExclusions policy setting).

           

      • #190985 Reply
        anonymous
        Guest

        No Issues with Windows 10 1803 here, then again I don’t run c**pware that makes my computer look like I’m running windows 98.

      • #191328 Reply
        anonymous
        Guest

        Susan,

        I just wanted to say THANK YOU!!!  Thanks for posting to this site.  YOU are a legend!

      • #191489 Reply
        anonymous
        Guest

        A few days after I installed 1803, I had an odd experience. Everything was normal until a couple of days after the installation, when I powered down the machine so that I could move it and connect it to a different power source. When I started it, I had to wait through a long disk drive cleanup that shouldn’t have been required, since this machine has never suffered an unexpected loss of power since I put it into service at the end of December 2017.

        Perhaps related to it, my System Restore history reported only a single restore point, which was associated with a software installation that I performed on Monday night.

        I have since applied the May 1803 Patch Tuesday update, and cycled the machine a couple of times. So far, nothing seems out of order.

      • #191494 Reply
        TXWizard_2018
        AskWoody Plus

        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.

        1. The font and color scheme of my command prompt windows reverted to the system defaults.
        2. Two custom context menu items in the File Explorer disappeared, while a third remained. The two that were discarded invoked system utilities (attrib.exe, with different switches), while the shortcut that was preserved invoked a custom system utility (Date2FN.exe) of my own devising that appends the last modified time to the base name of a file.

        David A. Gray

        Designing for the Ages, One Challenge at a Time

        1 user thanked author for this post.
      • #192519 Reply
        anonymous
        Guest

        I was getting near daily BSODs with 1709 related to having an AMD chipset. So, I upgraded to 1803 right away and have been crash free for 2 weeks now. I’m sorry others are having problems, but I’ve been pleased with the stability of 1803.

      • #192556 Reply
        columbia2011
        AskWoody Plus

        Found interesting topic on Reddit with discussion of new mess of Windows 10 April Update which Removes “Shutdown” without updating.

        Windows 10 April Update Removes "Shutdown" without updating from Windows10

        1 user thanked author for this post.
      • #194856 Reply
        Hailstorm
        AskWoody Plus

        Hi Susan and others

        I would like to point out an incompatibility with the 1803 upgrade on some ASUS systems (including one of mine … sigh)

        It’s covered fairly well in this thread:

        https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/updating-to-windows-10-version-1803-freezes-on-the/4bc7153c-16cf-4de0-8f8f-7c7d8fe94a56

        The symptoms are that the 1803 upgrade process hangs after the first restart.  One is left looking at the windows logo (no spinning dots, no disk activity).  Fortunately a hard reset brings everything back to a login screen.  1803 install fails with error code 0xc1900101.

        One solution seems to be turning off VT-d in the BIOS.  (Anyone know what this setting does?).

        I think I also found a thread where someone suggested a BIOS update might help.

        This may be worth tracking on your list.

        Cheers HS

        • #194859 Reply
          columbia2011
          AskWoody Plus

          Intel Virtualization Technology (VT-d) used for Hyper-V, vmware and another products of virtualization. Maybe your notebook processor does not support any virtualization.

          • #194974 Reply
            Hailstorm
            AskWoody Plus

            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.

            1 user thanked author for this post.
        • #197999 Reply
          Hailstorm
          AskWoody Plus

          Just in case anyone is interested in the VT-d saga (described above), my problem-PC has recently stopped being offered the 1803 update.  I take this as evidence that Microsoft have recognised the issue.  Hopefully they are preparing a fix!

          Cheers HS

      • #198808 Reply
        Mick Mickle
        AskWoody Plus

        The 1803 feature update stops some nForce/GeForce chipsets from waking up through Task Scheduler.  I have this problem with three computers, all Asus M3N78 Pro motherboards with GeForce 8300 chipset, and homed in on the issue when I read this recent post by BarryRyder:  Since Windows 10 1803 update scheduled tasks do not wake PC.

        This is a problem that might not become evident until you notice that a task didn’t run.  I had thought the 1803 update had gone well, but then found that Windows Server 2012 R2 Essentials would no longer wake them for backup.  After a bit of research on how Windows Server Essentials does the wake-up process, I found that it’s through a simple task in the scheduler.  Task settings were the same in the client computers that still got woken for backup as those that didn’t — all had “Wake this computer to run this task” checked.  I see this issue as another Win 10 update incompatibility with this AMD/NVIDIA chipset.  (Remember the problem with Meltdown & Spectre patches for AMD computers?)

      • #198961 Reply
        Mr. Natural
        AskWoody Plus

        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

        1 user thanked author for this post.
      • #203153 Reply
        Mick Mickle
        AskWoody Plus

        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.)

        1 user thanked author for this post.
    Viewing 39 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: Patch Lady – early trending issues with 1803

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.