Windows 10: KB4512534 for Windows 10 version 1809 fixes VB bug and more

Microsoft released the cumulative update KB4512534 for its Windows 10 version 1809 operating system on August 17, 2019.

The update follows the release of the updates KB4517297 for Windows 7 and Windows Server 2008 R2,
KB4517298 for Windows 8.1 and Windows Server 2012 R2, and KB4512494 for Windows 10 version 1709 which the company released on August 16, 2019.

KB4512534 is available on Windows Update, as a direct download on the Microsoft Update Catalog website, and on WSUS for organizations.

Note: We recommend that you back up the system partition before you install any updates on Windows machines. You may use free tools such as Macrium Reflect or Paragon Backup & Recovery Free for that.

KB4512534




Important links

• Support Article on Microsoft website
• Microsoft Update Catalog listing

The cumulative update fixes the VB bug that Microsoft acknowledged shortly after the release of the August 2019 Patch Day for Windows. The update addresses the long-standing Preboot Execution Environment issue as well.

Here is the list of fixes and changes in the release:

• Fixed an issue with Windows Hello not working after restarts.
• Improved reliability of push notifications about app deployments to Microsoft HoloLens 1 devices.
• Fixed an issue with downloading DRM files from certain websites in Edge an IE.
• Fixed an issue that prevented the Universal C Runtime Library from returning proper time zone global variables values.
• Fixed a Deployment Image Servicing and Management (DISM) issue that caused it to stop responding under certain conditions.
• Fixed a default keyboard issue that affected the English Cyprus (en-cy) locale.
• Fixed a Microsoft Edge printing issue so that PDF documents with portrait and landscape pages print correctly.
• Fixed another issue with PDF documents configured to be opened only once in Microsoft Edge.
• Addressed performance issues for the Win32 subsystem and Desktop Window Manager.
• Fixed an input and display of special characters issue when application used imm32.dll.
• Addressed a composition leak in UWP apps.
• Fixed a memory leak in dwm.exe that could lead to loss of functionality and cause a device to stop working.
• Fixed an automatic sign-in issue that affected the bypass Shift-key.
• Fixed a reporting issue in the Windows Management Instrumentation class Win32_PhysicalMemory.
• Fixed an issue that prevented App-V applications from opening.
• Fixed a User Experience Virtualization issue that prevented exclusion paths from working correctly.
• Fixed a Windows Defender Advanced Threat Protection issue that caused the program to prevent others from accessing certain files.
• Fixed an issue that caused workstations to stop working when users signed in using an updated user principal name.
• Fixed a Windows Defender Application Control issue that prevented third-party binaries to be loaded from UWP applications.
• Fixed a Trusted Platform Module issue that prevented TPM devices from being used for Next Generation Credentials.
• Fixed an issue that caused applications on a container host to lose connectivity.
• Fixed an issue that prevented some users from receiving a TTL value when being added as members of Shadow Principals.
• Addressed an issue with the disabled attribute of the input element, which didn’t allow a scope to be passed to the authorization endpoint.
• Fixed a leak issue in Windows notification sockets that caused the operating system to run out of ports.
• Fixed a server edition authentication issue.
• Fixed an issue that could break domain trust when the Recycle Bin was configured on the domain that carried the trust.
• Increased the number of supported interrupts per device to 512 on systems that have x2APIC enabled.
• Fixed the Preboot Execution Environment issue.
• Fixed the VB issue.

Known Issues


Microsoft lists four known updates (down from six). All known issues are not new.

• Certain operations on Cluster Shared Volumes may fail.
• Errors on devices with certain Asian language packs installed.
• Black screen on first logon after update installation issue.
• Apps and scripts that use the NetQueryDisplayInformation API or the WinNT provider equivalent may only return 50 or 100 entries.

Now You: Have you installed the new update (updates) that Microsoft released in August? What is your experience so far?

Ghacks needs you. You can find out how to support us here (https://www.ghacks.net/support/) or support the site directly by becoming a Patreon (https://www.patreon.com/ghacks/). Thank you for being a Ghacks reader. The post KB4512534 for Windows 10 version 1809 fixes VB bug and more appeared first on gHacks Technology News.

read more...

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

VBS Msgbox

Denis,

• I was too lazy to compute the size programmatically. And, it the 2005 version the message box always came up hidden, so I always used 0 for the top. It's also part of my OCD to be able to control everything.
• I personally don't need it to timeout. I used this in vbs files to ask to continue to the next step, skip the next step or cancel the vbs. BTW, I added the code back in but keep it assign it to 0.
• Sound was calling Windows Media Player: WshShell.Run "C:\Users\donast\desktop\sndrec32.lnk",7,false the lnk is a shortcut on my old desktop that had: "C:\Program Files (x86)\Windows Media Player\wmplayer.exe"
  "C:\Users\Public\Music\Wavefiles\Twilight.wav"
• Yes. The value is the number of the button in the order specified when calling it.
• Never really thought about it as all my VBS/VBA code is relatively simple and I add comments in the file as necessary to remind me what is going on. I don't usually have anyone to share my code.

FYI I use a VBS to call it. Here's a line from a test vbs I use to run your version:

choice=Wshshell.run("custommsgbox.vbs " & wscript.scriptname & " ""CopyFiles.vbs done. Continue with UnArchVista.vbs?"" ""White"" ""Black"" 40 ""Yes"" ""No"" ""Cancel""",1,true)

Copy it to a text editor to see all the spaces, etc. Took me a while back the to figure it out.

Don

 

Windows version 1809

The only real way to find out if 1809 still has bugs is to install it.

Microsoft released it before & it was full of nasty bugs.

Can you trust Microsoft to tell people the truth ?