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
  • More than two weeks later, still no VB/VBA/VBScript fix for Win10 version 1903

    Home Forums AskWoody blog More than two weeks later, still no VB/VBA/VBScript fix for Win10 version 1903

    This topic contains 13 replies, has 8 voices, and was last updated by  woody 3 weeks, 3 days ago.

    • Author
      Posts
    • #1924025 Reply

      woody
      Da Boss

      Fixing bugs introduced by Windows security patches be like: https://twitter.com/i/status/1165757143448018944
      [See the full post at: More than two weeks later, still no VB/VBA/VBScript fix for Win10 version 1903]

      3 users thanked author for this post.
    • #1924068 Reply

      Microfix
      Da Boss

      Great archive clip!
      SRV is still considered to be an historic accomplished world renowned guitarist/ musician and rightly so. RIP
      MS, however, needs tuning as the frets are worn, VBA strings stretched and pickups delayed..and we are the ones singing the blues.

      ********** Win7 x64/x86 | Win8.1 x64 | Linux Hybrids x64 **********

      2 users thanked author for this post.
      • #1924641 Reply

        willygirl
        AskWoody Plus

        Great archive clip! SRV is still considered to be an historic accomplished world renowned guitarist/ musician and rightly so

        The best! Gone too soon baby …

        Win7 SP1 Home 64-bit

    • #1924120 Reply

      zero2dash
      AskWoody Lounger

      Again, I have not had any issues with the August updates for 1903 with any VB applications. No errors, everything runs as it should.

    • #1925014 Reply

      Sproots
      AskWoody Plus

      Only have July Updates.

      Was pushed to 1903 from 1809 ISO creation on a new install last week (the MS creation download link specifically listed as 1809 at the time I downloaded weeks ago).

      User called just now to say they couldn’t print an office doc (.docx).

      Had office set to block all macros with notification, user doesn’t need them, and when opening this document gets the popup.

      Examined document and it does not contain any macros, just a word file with simple text.

      The error popup says that “opening” the document requires VBA language support.  Can I assume this is part of this issue?

      No problems opening an .xlxs file that does have formulas and one personal macro for adding new sheets.

       

      • This reply was modified 3 weeks, 4 days ago by  Sproots.
    • #1925136 Reply

      abbodi86
      AskWoody_MVP

      Improving the Windows 10 update experience with control, quality and transparency

      Expanding Release Preview

      The final May 2019 Update build will spend increased time in the Release Preview Ring of the Windows Insider Program, allowing us to gather more feedback and insights on compatibility and performance at scale before making the update more broadly available.

      I guess that apply to non-security CU as well

      KB4512941 (18362.325) and KB4512941 (18362.327) are in the RP ring
      they could go public tonight or on Friday

      1 user thanked author for this post.
      • #1925194 Reply

        Microfix
        Da Boss

        ..my guess would be Friday.
        Woody, looks like ‘Week D’ patches on the MS Catalog today for W10, 2016 and 2019 server!
        microcode updates.. Yawn

        ********** Win7 x64/x86 | Win8.1 x64 | Linux Hybrids x64 **********

        1 user thanked author for this post.
        • #1925559 Reply

          geekdom
          AskWoody Plus

          Friday patches are a poor concept and some version of the Friday night dump. If the system hurls, there’s no help available through the weekend nor holiday Monday.

          Group G{ot backup} TestBeta
          Win7Pro · x64 · SP1 · i3-3220 · RAM 8GB · Firefox: uBlock Origin - NoScript · HDD · Canon Printer · Microsoft Security Essentials · Windows: Backup - System Image - Rescue Disk - Firewall
          • This reply was modified 3 weeks, 3 days ago by  geekdom.
      • #1925378 Reply

        woody
        Da Boss

        My Release Preview test machine is at 18362.327.

        Guess I’m not going to be part of the 10%….

    • #1925557 Reply

      EP
      AskWoody_MVP

      ditch .327 woody.

      build 18362.329 of KB4512941 just came out in the RP ring as noted in this comment from Deskmodder.de:
      https://www.deskmodder.de/blog/2019/08/27/kb4512941-windows-10-1903-18362-325-manueller-download-kb4515530-als-ssu/#comment-109468

      this may delay the official release of KB4512941 a little further

      • This reply was modified 3 weeks, 3 days ago by  EP.
      1 user thanked author for this post.
      • #1925869 Reply

        woody
        Da Boss

        I keep clicking Check for updates, and I’m still on 18362.327

        Oh boy.

      • #1925886 Reply

        woody
        Da Boss

        Also note that there was a truly obfuscatory update added to the 19H2 announcement, yesterday.

        UPDATE 8/29: We have released 19H1 Build 18362.329 and 19H2 Build 18363.329 to Windows Insiders in the Release Preview ring with the following fixes:

        • We fixed an issue where on devices with LTE capability, some SIM cards from certain carriers would not work correctly.

        • We fixed several issues resulting in bugchecks on some devices.

        To offer a clarification on these releases – 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package. For the small subset of Windows Insiders (the 10%) in Release Preview who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the 19H2 features. This *changes* the build number for the OS from 19H1 Build 18362 to 19H2 Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between 19H1 and 19H2. As we continue to test our servicing packages in the Release Preview ring, Insiders on 19H1 and 19H2 will get a single Cumulative Update with the same fixes.

        If that’s a clarification, I’m an unkey’s monkle.

        I see that 18362.329 and 18363.329 have been added to the ChangeWindows list, so they’re definitely out in the wild.

        • This reply was modified 3 weeks, 3 days ago by  woody.
    • #1926183 Reply

      EP
      AskWoody_MVP

      KB4512941 update officially on Microsoft Update Catalog (both 32bit & 64bit versions) FRI Aug. 30 at 10:10am local pacific time [build 18362.329] 🙂

      http://www.catalog.update.microsoft.com/Search.aspx?q=4512941

      MS did not release KB4512941 sooner because of some recent problems discovered in older versions of KB4512941 (see, THAT’S why MS takes it time in doing patches for latest Win10 version and not rushing them for public release)

      • This reply was modified 3 weeks, 3 days ago by  EP.
      • This reply was modified 3 weeks, 3 days ago by  EP.
      1 user thanked author for this post.
      • #1926220 Reply

        woody
        Da Boss

        … and JUST in time for my Computerworld article, which takes MS to task for the delay.

        Sigh.

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

    Reply To: More than two weeks later, still no VB/VBA/VBScript fix for Win10 version 1903

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