Station-Drivers - Windows 10 v1903 RTM aka MAY 2019 Update - Page 6 - STATION-DRIVERS

Windows 10 v1903 RTM aka MAY 2019 Update

Plus d'informations
il y a 5 mois 2 semaines - il y a 5 mois 2 semaines #1815 par erpster96
thanks SM-003.

though I have decided to revert from 1903 to an older version like 1809 on some of my PCs as I have recently found some minor issues with 1903.

https://www.neowin.net/news/microsoft-is-now-letting-users-know-when-their-pc-isnt-ready-for-the-may-2019-update

https://www.askwoody.com/2019/bugs-with-win10-1809-june-cumulative-update-and-realtek-bluetooth-avast-wont-play-with-1903/

I may upgrade again to 1903 when the July or Aug. 2019 CUs for v1903 come out. still some bugs to iron out w/ 1903 though it should work well with many modern PCs made in the past few years. but running 1903 on very old PCs is a different story.
Dernière édition: il y a 5 mois 2 semaines par erpster96.

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 5 mois 2 semaines #1816 par SM-003

erpster96 écrit: thanks SM-003.

though I have decided to revert from 1903 to an older version like 1809 on some of my PCs as I have recently found some minor issues with 1903.

https://www.neowin.net/news/microsoft-is-now-letting-users-know-when-their-pc-isnt-ready-for-the-may-2019-update

https://www.askwoody.com/2019/bugs-with-win10-1809-june-cumulative-update-and-realtek-bluetooth-avast-wont-play-with-1903/

I may upgrade again to 1903 when the July or Aug. 2019 CUs for v1903 come out. still some bugs to iron out w/ 1903 though it should work well with many modern PCs made in the past few years. but running 1903 on very old PCs is a different story.


What's the problem that you're facing in 19H1?
Les utilisateur(s) suivant ont remercié: kinkyleather

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 5 mois 2 semaines - il y a 5 mois 2 semaines #1840 par ex58
New Cumulative updates for 1903 (18362.207) KB4501375:
Windows Insiders in the Release Preview ring

x64:
download.windowsupdate.com/c/msdownload/...e126c6b0f8aee9c5.cab

x86:
download.windowsupdate.com/c/msdownload/...ceb4af67e76f5a0d.cab
Dernière édition: il y a 5 mois 2 semaines par ex58.

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 5 mois 2 semaines #1845 par admin
Passage fait en mode forcing car la mise à jour bloquai 1260 et j'ai trouvé, une put…. de clé USB qui me bloquai l'upgrade. 1234

Msi Z390 Tomahawks, Intel i5 (9600KF), 16Go Corsair RVB, SSD970, SSD960/860/850, nVidia GeForce GTX960, Creative SB X-Fi Titanium, Clavier Corsair RVB, Souris Asus Gladius II RGB, Grand tour Enermax, Tapis RGB corsair, Router RT2600, Free Fibre 1Gbs (Cat 7&8)

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 5 mois 2 semaines #1846 par SM-003
v207 installed & running perfectly here from the latest released CAB file, no need to put it in any SubDIR as I install it directly from where it's downloaded & stored


Just make sure you install the latest SSU windows10.0-kb4506933-x64 first before installing the latest CU, then reboot the system, after that install the CU windows10.0-kb4501375-x64.

If still getting the error then the WSUS service is broken, do an in-place upgrade/update to solve that.
Pièces jointes :

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 5 mois 1 semaine #1853 par SM-003
June 27, 2019—KB4501375 (OS Build 18362.207)
Improvements and fixes
This update includes quality improvements. Key changes include:

Addresses an issue that fails to display the cursor when you hover over the keyboard magnifier.
Addresses an issue with looping redirects between Microsoft Edge and Internet Explorer 11.
Addresses an issue with Scalable Vector Graphics (SVG) marker display.
Addresses an issue with programmatic scrolling in Internet Explorer 11.
Addresses an issue with displaying portions of a webpage that has many elements and multiple nesting levels under certain conditions in Internet Explorer.
Addresses an issue that may cause “Error 1309” while installing or uninstalling certain types of .msi or .msp files on a virtual drive.
Addresses an issue that may cause Night light, Color Management profiles, or gamma correction to stop working after shutting down a device.
Addresses an issue that only shows grey scale in the camera during Windows Hello enrollment.
Addresses an issue that may cause playback of some video content generated by iOS devices to fail.
Addresses a desktop and taskbar flickering issue on Windows Server 2019 Terminal Server that occurs when using User Profile Disks.
Addresses an issue that allows users to disable the sign-in background image when the "Computer\Administrative Templates\Control Panel\Personalization\Prevent changing lock screen and logon image" policy is enabled.
Addresses a disconnection issue when using fitness software on an Android phone that has the Your Phone application installed.
Addresses an issue that prevents the Windows Event Log service from processing notifications that the log is full. This makes event log behaviors, such as archiving the log when it reaches a maximum file size, impossible. Additionally, the Local Security Authority (LSA) cannot handle CrashOnAuditFail scenarios when the Security log is full, and events cannot be written.
Addresses an issue that causes Office 365 applications to stop working after opening when they are deployed as App-V packages.
Addresses an issue that may prevent Container Hosts from receiving an address from a Dynamic Host Configuration Protocol (DHCP) server.
Addresses an issue that may prevent some upgrades from Windows 7 from completing successfully when third-party antivirus software is installed.
Reinforces the Certificate Revocation List (CRL) on Internet Key Exchange version 2 (IKEv2) machines for certificate-based virtual private network (VPN) connections, such as Device Tunnel, in an Always On VPN deployment.
Addresses an issue that triggers a Group Policy update even when there are no policy changes. This issue occurs when using the client-side extension (CSE) for folder redirection.
Addresses an issue that may prevent the Preboot Execution Environment (PXE) from starting a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.
Addresses an issue that may display the error, “MMC has detected an error in a snap-in and will unload it.” when you try to expand, view, or create Custom Views in Event Viewer. Additionally, the application may stop responding or close. You may also receive the same error when using Filter Current Log in the Action menu with built-in views or logs.
Addresses an issue with WinHTTP registrations that increase the registry size and delay the operating system’s startup. This occurs on devices that use proxy auto-config (PAC) files to define how web browsers and agents select an appropriate proxy server. To stop the incremental growth of the registry, update the following:
Path: HKEY_CURRENTUSER\"Software\Classes\Localettings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Mappings"

Setting: CleanupLeakedContainerRegistrations

Type: DWORD

Value: 1

A value of 1 removes preexisting registrations; a value of 0 (default) retains existing registrations.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

Windows Update Improvements

Microsoft has released an update directly to the Windows Update client to improve reliability. Any device running Windows 10 configured to receive updates automatically from Windows Update, including Enterprise and Pro editions, will be offered the latest Windows 10 feature update based on device compatibility and Windows Update for Business deferral policy. This doesn't apply to long-term servicing editions.

Known issues in this update

Symptom
Windows Sandbox may fail to start with "ERROR_FILE_NOT_FOUND (0x80070002)" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Workaround
Microsoft is working on a resolution and will provide an update in an upcoming release.


Link for newly released CU, SSU & DotNet CU
Les utilisateur(s) suivant ont remercié: Tom

Connexion ou Créer un compte pour participer à la conversation.

Temps de génération de la page : 0.967 secondes