Windows 10

mrbell1984 said:
I can echo that. :) Got to be hardware specific. Certain hardware gets certain problems.
Click to expand...

I don't think it is hardware specific but it does seem specific in some way - my dad for instance on both his laptop and desktop Windows 10 usually updates in like 10 minutes, never had any issues except a couple of times Windows update decided to take matters into its own hands when he was actually wanting to use the machine. While over the spread of systems I have on 10 it is a very different story.

What gets me though - I have 2 identical hardware 2 in 1 devices that I run off the same image and after an update with no rhyme or reason not infrequently one will get its knickers in a twist and the other will be fine, despite them being deployed off exactly the same base, but it is completely random which it is - I'd put them on 7 only the hardware is only supported on 10 or newer.
 
This is what happened one of the times after an update LOL:

3qodyKH.png


That was right off a fresh deploy to both as well - exactly the same data on the drives but one came up with that LOL. (To my knowledge both machines are stable in terms of CPU and RAM so not like random corruption due to that).
 
Well the software has to detect certain hardware so when things go wrong like that I can only think that it's reporting back as something else or miss reading something in the hardware. I don't think I have ever seen something like that before either. That seems nuts.
 
mrbell1984 said:
Well the software has to detect certain hardware so when things go wrong like that I can only think that it's reporting back as something else or miss reading something in the hardware. I don't think I have ever seen something like that before either. That seems nuts.
Click to expand...

Something is quite broken there - it isn't quite apparent at first glance but the estimated time to full charge is a slider for instance not the usual ETA and several options were just default ones on the form (usually hidden unless used) that were showing and non-functional not just the information being displayed being wildly wrong. While it only happened to a small number of people I wasn't the only one that had similar happen with that lot of updates. The odd thing was how it happened to one system and not the other despite almost everything being equal.
 
Latest bug fix patch for v1909 is out (optional).

KB4535996

  • Addresses an issue that prevents the speech platform application from opening for several minutes in a high noise environment.
  • Addresses an issue that reduces the image quality in the Windows Mixed Reality (WMR) home environment.
  • Improves Urlmon resiliency when receiving incorrect Content-Length for a PeerDist response.
  • Addresses an issue with rendering PeerDist-encoded content in Internet Explorer and Microsoft Edge.
  • Addresses an issue that might prevent ActiveX content from loading.
  • Addresses an issue that might cause Microsoft browsers to bypass proxy servers.
  • Improves the battery performance during Modern Standby mode.
  • Addresses an issue that prevents Centennial apps from opening in certain scenarios.
  • Addresses an issue that prevents the OpenFile() function in the KernelBase.dll library from handling file paths longer than 128 characters.
  • Addresses an issue that prevents a user from upgrading or uninstalling some Universal Windows Platforms (UWP) apps in certain scenarios.
  • Addresses an issue that causes Microsoft Narrator to stop working when a user session is longer than 30 minutes.
  • Addresses an issue that adds an unwanted keyboard layout as the default after an upgrade or migration even if you have already removed it.
  • Addresses an issue with editing the properties of .mov files.
  • Addresses an issue that causes usbvideo.sys to stop working intermittently when a device resumes from Suspend or Sleep after using the Camera app or Windows Hello.
  • Addresses an issue that might prevent the "Allow uninstallation of language features when a language is uninstalled" Group Policy from taking effect.
  • Addresses an issue that prevents the Windows Search box from rendering fully in the space allotted for it.
  • Addresses an issue that prevents the Input Method Editor (IME) user dictionary from being used when leveraging folder redirection with user profiles.
  • Addresses an issue that might prevent the Windows Search box from showing results.
  • Addresses an issue that causes the installation process to stop responding when installing Windows on a VMware guest machine that has a USB 3.0 hub attached.
  • Addresses an issue with Windows Autopilot self-deploying mode and white glove deployment.
  • Addresses an issue in which re-running PowerShell workflows might fail with compilation errors for long sessions.
  • Improves Event Forwarding scalability to ensure thread safety and increase resources.
  • Addresses an issue in the Windows activation troubleshooter that prevents users from reactivating their copy of Windows using the product key stored in their Managed Service Account (MSA).
  • Addresses an issue that prevents some applications, which are deployed using the Microsoft Installer (MSI) from being installed using the mobile device management (MDM) platform. This issue occurs because of a missing property in the MSI metadata.
  • Addresses an issue that generates an “unknown username or bad password” error when attempting to sign in. This occurs in an environment that has a Windows Server 2003 domain controller (DC) and a Windows Server 2016 or later DC.
  • Addresses an issue with sign in scripts that fail to run when a user signs in or signs out.
  • Addresses an issue that continues to collect IsTouchCapable and GetSystemSku data when they should no longer be collected.
  • Addresses an issue that causes some Azure Active Directory (AAD) joined systems, which were upgraded to Windows 10, version 1903, to erroneously rejoin the AAD domain.
  • Addresses an issue in which the WinHTTP AutoProxy service does not comply with the value set for the maximum Time To Live (TTL) on the Proxy Auto-Configuration (PAC) file. This prevents the cached file from updating dynamically.
  • Addresses an issue that causes the wrong printer name to be selected when you click the Print button in the SQL reporting service.
  • Addresses an issue that prevents the printer settings user interface from displaying properly.
  • Addresses an issue in the Network Profile Service that might cause a computer to stop responding.
  • Addresses an issue that prevents some applications from printing to network printers.
  • Addresses an issue that might cause a printer to be a hidden device in Device Manager after a restart.
  • Addresses an issue that causes Host Networking Service (HNS) PortMapping policies to leak when the container host is reinstated after a restart.
  • Addresses a stop error (0x000000CA) that occurs when you mount a Resilient File System (ReFS) volume without a physical device. This might occur in some backup solution scenarios.
  • Addresses an Open Database Connectivity (ODBC) issue that causes an infinite loop in the retry logic when there are several lost connections in the connection pool.
  • Addresses an issue that causes the Local Security Authority Subsystem Service (LSASS) to stop working and triggers a restart of the system. This issue occurs when invalid restart data is sent with a non-critical paged search control.
  • Addresses an issue that intermittently generates Online Certificate Status Protocol (OSCP) Responder audit event 5125 to indicate that a request was submitted to the OCSP Responder Service. However, there is no reference to the serial number or the domain name (DN) of the issuer of the request.
  • Addresses an issue that causes queries against large keys on Ntds.dit to fail with the error, “MAPI_E_NOT_ENOUGH_RESOURCES”. This issue might cause users to see limited meeting room availability because the Exchange Messaging Application Programming Interface (MAPI) cannot allocate additional memory for the meeting requests.
  • Addresses an issue that corrupts a log file when a storage volume is full and data is still being written to the Extensible Storage Engine Technology (ESENT) database.
  • Addresses an issue that causes _NFS4SRV_FILE_CACHE_ENTRY and DirectoryCacheLock to stop responding and leads to error 9E.
  • Addresses an issue that prevents Server Message Block (SMB) Multichannel from working within a cluster network that has IPv6 Local-Link addresses.
  • Addresses an issue that might cause Storage Migration Service inventory operations on a Windows Server 2003 source computer to fail in clustered environments.
  • Addresses a timing issue that may cause stop error 0x27 in mrxsmb20!Smb2InvalidateFileInfoCacheEntry. This issue occurs when you rename or delete files that have certain extensions and are stored on a network share that has client-side caching enabled.
  • Addresses an issue in the Storage Migration Service that causes the Cutover stage to stop working during migration if an administrator assigns a static IP address to the source adapter.
  • Addresses an issue in which canceling a deduplication (dedup) job to rebuild hotspots prevents other deduplicationPowerShell commands from responding.
  • Addresses an issue that might cause Remote Desktop sessions to disconnect because a leak in system memory occurs when the client window is minimized or maximized.
  • Addresses an issue that makes the Windows Defender Application Control’s Code Integrity-based events unreadable.
  • Addresses an issue with certificate validation that causes Internet Explorer mode on Microsoft Edge to fail.
Click to expand...

Got no issues here, so its a pass. :p

Also had a cumulative for the .NET Framework too (KB4537572).
 
mrbell1984 said:
I never got it tother day it only appeared after I did this update and rebooted.

What's your winver? (mines 18363.693)
Click to expand...

Same as yours now, as i figured, if its going to install automatically a week on Tuesday, i may as well just install it now, so i did, and be one less update then too :D

EDIT:

Id assume, before i installed this update, id have still been on build 18363.657.
 
You must log in or register to reply here.
Back
Top Bottom