Windows 10: Microsoft explains how Dynamic Updates work on Windows 10

Dynamic Updates play a role when Windows 10 feature updates are installed on a PC; this can be as part of a new installation or an update, e.g. from Windows 10 version 1809 to the May 2019 Update.

Dynamic Updates are supported by previous versions of Windows, including Windows 8.1 or Windows Server 2012.

Dynamic Updates are enabled by default but can be disabled by the user or system administrator. Their main purpose is to download certain components relevant to the update process or system stability during installation.

Without Dynamic Updates, a system's administrator would have to install certain components, e.g. new cumulative updates or updated drivers, after the initial installation.

Windows 10 Dynamic Updates




Dynamic Updates may include the following components according to Microsoft:

• Setup -- Fixes for files required for Setup.
• SafeOS -- Fixes for the Safe OS which Microsoft uses to update the recovery environment.
• Servicing Stack Update (SSU) / Critical -- Address any Servicing Stack Update issues.
• Latest Cumulative Updates / General Distribution Release -- Installs the latest cumulative update for the operating system version.
• Language Pack / Feature on Demand -- To preserve language packs and optional features.
• Driver -- Drivers targeted for Dynamic Update release.

The Dynamic Update step is one of the first that Windows Setup invokes during installation. It involves contacting Microsoft and retrieving updated content that is then applied to the installation media.

Windows 10 Setup reaches out to the HTTPS endpoint, i.e. the Internet-facing URL hosted by Microsoft, fetches the Dynamic Update content, then applies those updates to your OS installation media..
​

Windows Setup displays a prompt to users, "Get updates, drivers, and optional features" during installation that gives users control over the process. The default and recommended option is to download and if users select that option, Dynamic Updates are used. It is possible to deny that during installation.

Unattended installations supports a setting to disable Dynamic Updates. The default is set to True which means that Dynamic Updates are enabled by default. You may set this to False to disable Dynamic Updates.

<DynamicUpdate>
<Enable>True</Enable>
</DynamicUpdate>
​

Setup.exe supports a command line parameter that defines whether Dynamic Updates are used. Use /DynamicUpdate {enable | disable} to set the feature to on or off. The command setup /auto upgrade /DynamicUpdate disable would disable Dynamic Updates.

Closing words


Dynamic Updates may resolve certain installation or update related issues during setup. The feature is useful as it can resolve update or installation related issues during setup, but it can also lead to issues caused by these updated or extra components.

Now You: How do you install or upgrade Windows?

Ghacks needs you. You can find out how to support us here or support the site directly by becoming a Patreon. Thank you for being a Ghacks reader. The post Microsoft explains how Dynamic Updates work on Windows 10 appeared first on gHacks Technology News.

read more...

 

Creative X-Fi Soundcards and Windows 10 Fall Creators Update 1709 = Complete Disaster / Not Working

Thank you for trying to help , i did tried your suggestion but it did not work :/ , nothing seems to make it work on Windows 10 Fall Creators Update 1709. In the meantime i have bought a new SoundBlasterX AE-5 and it did installed flawlessly , no problems whatsoever. it is up to Creative ( drivers ) and Microsoft ( bug fix ) to fix this huge bugs with Audio.

Kind Regards: Chispy

 

Microsoft blocks Windows 10 April Update for Intel SSD 600p Series

Microsoft is blocking some Intel SSDs from installing the April 2018 Update after discovering an incompatibility issue that causes performance and stability issues. In short, the problem was explained by Microsoft as: “When attempting to upgrade to Window 10 April 2018 Update select devices with certain Intel SSDs may enter a UEFI screen reboot or crash repeatedly.” Microsoft says that this issue has no workaround and that those that have attempted to update Windows 10 to the Windows 10 April 2018 Update should revert back to Windows 10 Fall Creators Update version 1709.

Unfortunately, the announcement by Microsoft fails to list what specific Intel SSD models are having issues with the OS update. We contacted Intel and discovered that the Intel SSD 600p Series of client drives that was first introduced to the market in 2016 is the most popular drive that is having issues.

Source: Legit Reviews

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer