Eh, però la ver. 1903 è precedente a questo update, sei sicuro che comprenda tutti i Key changes postati da yeppala? :D

ma è l'ultima rilasciata no?

https://forums.mydigitallife.net/thr...release.79259/

E' la build che si è portato quando è tornato indietro nel tempo di due settimane :asd:

Chissà se usa uno Stargate o una DeLorean :asd:

Devio ridere :asd: o devo piangere :cry: alla domanda posta ? :)

E' ovvio che l' update del kb riguarda la versione di October W10, non c' entra mica con W10 April Update ? :)

In più, dimmelo tu.........;)




Degli aggiornamenti dopo aver installato W10 versione 1903, ci sono stati, ma non c' entrano nulla con questo kb :) Cronologia Aggiornamenti >

Avere una build più recente ma più vecchia di una build di una versione precedente ... andremmo incontro ad un paradosso spazio temporale e nessun computer sopravviverebbe dopo :asd:

Non facciamoci venire certi dubbi o perplessità :asd:

Da quello che so lo store nella enterprise "normale" c'è, così come Cortana, Edge e le altre App preinstallate. È assente nella LTSx, cioè LTSB e LTSC.

Per avere le idee chiare

https://www.cwi.it/sistemi-operativi...10-ltsb-109849

Troppo tardi, ormai gli sono venuti....
Povero tallines....:muro:

Anche al suo pc, non sa più cosa deve computare ... :asd:

Ho una domanda fatta dalla scimmia che mi assilla, installando l'ultima iso 18362.1 che non è ancora ufficiale, se domani esce quella ufficiale che si chiamerà esempio 18362.2, quella attuale si aggiornerà tramite WU e diventerà come release ufficiale, o rimarrà sempre insider preview?! spero di aver spiegato bene grazie.
PS
Vorrei capire se ci sono diversità tali che alla fine devo formattare nuovamente(preferendo sempre installazione pulita), oppure non mi cambierà praticamente nulla tra questa insider e quella ufficiale.

Si intendevo la LTSB e LTSC .
Non ho nessun dubbio, siete voi che siete indietro.......:asd: :asd: :Prrr: :Prrr: :ciapet:

Il mio pc funziona benissimo :ciapet:

Beh poi questa supera tutte,:asd: , se evitavi forse facevi una figura migliore......forse hai provato tramite satellite e il collegamento non è partito :asd:........

https://www.hwupgrade.it/forum/showp...ostcount=36228

Ma Fatal vediamo di dire cose che corrispondono a verità, per piacere ehhh, anche perchè se spari ste c...@@te, fai solo disinformazione............quindi........:)

Credo che, come sempre, quando uscirà l'aggiornamento ufficiale le versioni verranno allineate.
Una domanda per chi ha già installato la 1903: ho iniziato (solo iniziato) la procedura di aggiornamento su 2 PC, uno con BIOS e uno UEFI e, a differenza dei precedenti major update, su ambedue la prima cosa che mi è stata chiesta è stato il Product Key, senza il quale non è possibile andare avanti.



Voi che avete fatto? Avete inserito un PK a caso o siete andati a recuperare il PK originario?

Ossia ha fatto l' intallazione in place dell' Iso di W10 April 2019 Update cosi ? > https://www.hwupgrade.it/forum/showp...9&postcount=10
Io ho fatto l' installazione in place della 1803, della 1809 e dell' ultima Versione di W10, che è la 1903, ma non mi ha mai chiesto il product-key ... :boh:

Che poi, vien da pensare, se la versione precedente di W10 in questo la 1809, su cui vai a installare la Nuova versione > la 1903, è già attivata, perchè dovrebbe chiedere il product-key ?..........

Impossibile perché non è ancora disponibile l'iso della 1903.

Sgombriamo il campo dall'equivoco, quello che avete installato non è ancora la versione ufficiale Microsoft per tutti, può sempre cambiare prima del rilascio ufficiale definitivo, di cui non si sa neanche la data finora.

Le versioni ufficiali delle release di Windows 10 sono quelle che vengono fornite con il MediaCreationTool, e per il momento si limitano alla 1809.

Anch'io ho sempre fatto così, estraendo l'.iso su una pennetta e lanciando il setup da Windows, e non mi ha mai chiesto nulla, per questo la novità mi è parsa strana e non sono andato avanti con l'installazione....

Quella ufficiale no, quella insider si....

grosso update apparso poco fa per la build 1809

si arriva alla .404

Appunto, non è ancora l'ufficiale per tutti, possono esserci cose da ritoccare o aggiungere/togliere.

:old:

lol ho solo letto male la build :asd:

edit:


April 2, 2019—KB4490481 (OS Build 17763.404)


Improvements and fixes
This update includes quality improvements. Key changes include:

Addresses an issue that occurs on machines that have multiple audio devices. Applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. Examples of applications that may stop working include Windows Media Player, Realtek HD Audio Manager, and the Sound Blaster Control Panel.

Includes a fix for Game Mode that ensures the feature will no longer impact your experiences when using the industry’s top streaming and recording software.
Enables activation of insider builds of Windows 10 Enterprise for Virtual Desktops in Microsoft Azure. Microsoft Azure is the only tested and supported platform to host Windows 10 Enterprise for Virtual Desktops, which is a key part of Windows Virtual Desktop.

Addresses an issue that may cause the loss of Favorites or the Reading List in Microsoft Edge after updating the operating system.
Addresses an issue that causes Internet Explorer to randomly stop working while browsing.
Addresses an issue with scrolling ActiveX content in a window in Internet Explorer 11 during a user-triggered scroll operation.
Addresses an issue that prevents the operating system from loading new icon files if it encounters a badly formatted icon file.
Updates time zone information for São Tomé and Príncipe.
Updates time zone information for Kazakhstan.
Updates time zone information for Buenos Aires, Argentina.
Addresses an issue that prevents the “Turn off app notifications on the lock screen" policy from working. The path is "Computer Configuration\Administrative Templates\System\Logo".
Addresses an issue in which the graphics device interface (GDI) DeleteObject() may cause the calling process to stop working when both of the following conditions are true:
The calling process is a WOW64 process that handles memory addresses larger than 2 GB.
The DeleteObject() is called with a device context that is compatible with a printer device context.
Addresses an issue that prevents applications and callers from connecting to destination endpoints when they use network interfaces that don’t have a default gateway. This issue affects the following:
Internet access fails on devices with DSL modems and PPPoE dial-up Internet connections (commonly used with DSL modems).
Modern and Microsoft Store apps behave as if there is no Internet access on devices with DSL modems.
Web browsers and Win32 applications that are connected to the Internet are not affected by this issue.

Addresses an issue that causes Windows to reuse an expired Dynamic Host Configuration Protocol (DHCP) lease if the lease expired while the OS was shutdown.
Addresses an issue that causes the RemoteApp window to come to the foreground and to always remain active after closing a window.
Addresses an issue that prevents the authentication credentials dialog from appearing when an enterprise web server attempts to connect to the Internet.
Addresses an issue that may prevent Modern apps icons from appearing in the Taskbar and the Task Switcher during a RemoteApps connection.
Addresses an issue that causes certain Microsoft Store applications to fail to launch or stop working, including WeChat on the Universal Windows Platform (UWP).
Addresses an issue that fails to register USB cameras correctly for Windows Hello after the out of box experience (OOBE) setup.
Adds a new Group Policy setting called “Enable Windows to soft-disconnect a computer from a network”. This determines how Windows will disconnect a computer from a network when it determines that the computer should no longer be connected to the network.

If enabled, Windows will soft-disconnect (disconnection is not immediate or abrupt) a computer from a network.
If disabled, Windows disconnects a computer from a network immediately.
If not configured, the default behavior is soft-disconnect. For more information about soft-disconnect, see Understanding and configuring Windows Connection Manager.
Path: Computer Configuration\Policies\Administrative Templates\Network\Windows Connection Manager

Addresses an issue that prevents a virtual smart card from starting when running in conjunction with Citrix 7.15.2000 Workstation VDA software.
Addresses an issue that prevents users from configuring their screens for high-dynamic-range (HDR) video playback.
Addresses an issue with the Windows lock screen that prevents users from unlocking a device after multiple smart card users have used the same device. This issue occurs when you attempt to use a workstation that another user has locked.
Addresses a memory leak that occurs when a system processes logon sessions.
Addresses an issue that causes Always-On VPN exclusion routes to only work for link-local exclusions.
Addresses an issue that causes certificate renewal to fail when using CERT_RENEWAL_PROP_ID with the ICertPropertyRenewal interface.
Addresses an issue that mutes the sound of single-use applications, typically used in kiosk scenarios, after the system resumes from Sleep.
Addresses an issue to meet GB18030 certificate requirements.
Addresses an issue that slows server performance or causes the server to stop responding because of numerous Windows firewall rules. To enable this solution, use regedit to modify the following and set it to 1:
Type: “DeleteUserAppContainersOnLogoff” (DWORD)
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy
Addresses an issue that prevents the decryption of data using Windows 10, version 1703 or later versions of Windows. This issue occurs if you encrypted that data using DPAPI-NG or a group-protected PFX file on Windows 10, version 1607, Windows Server 2016, or earlier versions of Windows.
Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
Addresses minor issues with unknown options (unknown OPT) in the Extension Mechanisms for DNS (EDNS) for the Windows DNS Server role.

Addresses a timing issue that may result in an access violation when configuring Switch Embedded Teaming (SET).

Addresses an issue with the Remove-StoragePool PowerShell cmdlet that fails to clear pool metadata on NVDIMM physical disks.

Enables X2APIC support for AMD platforms to support 256 or more logical processors on Windows Server 2019.

Addresses an issue that prevents date parsers from converting future and past dates (Gregorian and Japanese) in compound documents (formerly OLE) to a relevant Japanese Era date. For more information, see KB4469068.

Addresses an issue that prevents users from enabling gan-nen support for the Japanese Era. For more information, see KB4469068.

Addresses an issue that causes slow screen refresh rates when an application creates and destroys many child windows.

Address an issue that causes the Start menu layout to reset or reset at every logon after an in-place upgrade to Windows 10, version 1809 from previous versions of Windows.

Addresses an issue that causes Wdiwifi.SYS to stop working with the error “7E (0xc0000005)”. This issue occurs when a client device is roaming between wireless access points (WAP) that have the same BSSIDs on the 2.4 Ghz and 5 Ghz bands.
If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.


Known issues in this update
Symptom Workaround
After installing this update, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:

Cache size and location show zero or empty.
Keyboard shortcuts may not work properly.
Webpages may intermittently fail to load or render correctly.
Issues with credential prompts.
Issues when downloading files.
Create unique user accounts so that two people don’t share the same user account when logging on to a Windows Server machine. Additionally, disable multiple RDP sessions for a single user account for a specific Windows Server.

Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing this update, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing this update, Custom URI Schemes for Application Protocol handlers may not start the corresponding application for local intranet and trusted sites on Internet Explorer.
Right-click the URL link to open it in a new window or tab.

Or

Enable Protected Mode in Internet Explorer for local intranet and trusted sites.

Go to Tools > Internet options > Security.
Within Select a zone to view or change security settings, select Local intranet and then select Enable Protected Mode.
Select Trusted sites and then select Enable Protected Mode.
Select OK.
You must restart the browser after making these changes.

Microsoft is working on a resolution and will provide an update in an upcoming release.
After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start 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.
To mitigate the issue, disable the Variable Window Extension on WDS server using one of the following options:

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

Open Windows Deployment Services from Windows Administrative Tools.
Expand Servers and right-click a WDS server.
Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.
Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

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

If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen will appear at startup. This is not a common setting in non-Asian regions.
To avoid this issue, don’t enable per font EUDC. As an alternative, you can edit the registry to mitigate this issue; for more information, see KB4496149.

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