Quantcast
  • Login
    • Account
    • Sign Up
  • Home
    • About Us
    • Catalog
  • Search
  • Register RSS
  • Embed RSS
    • FAQ
    • Get Embed Code
    • Example: Default CSS
    • Example: Custom CSS
    • Example: Custom CSS per Embedding
  • Super RSS
    • Usage
    • View Latest
    • Create
  • Contact Us
    • Technical Support
    • Guest Posts/Articles
    • Report Violations
    • Google Warnings
    • Article Removal Requests
    • Channel Removal Requests
    • General Questions
    • DMCA Takedown Notice
  • RSSing>>
    • Collections:
    • RSSing
    • EDA
    • Intel
    • Mesothelioma
    • SAP
    • SEO
  • Latest
    • Articles
    • Channels
    • Super Channels
  • Popular
    • Articles
    • Pages
    • Channels
    • Super Channels
  • Top Rated
    • Articles
    • Pages
    • Channels
    • Super Channels
  • Trending
    • Articles
    • Pages
    • Channels
    • Super Channels
Switch Editions?
Cancel
Sharing:
Title:
URL:
Copy Share URL
English
RSSing>> Latest Popular Top Rated Trending
Channel: Windows – Born's Tech and Windows World
NSFW?
Claim
0


X Mark channel Not-Safe-For-Work? cancel confirm NSFW Votes: (0 votes)
X Are you the publisher? Claim or contact us about this channel.
X 0
Showing article 1361 to 1380 of 4454 in channel 63679675
Channel Details:
  • Title: Windows – Born's Tech and Windows World
  • Channel Number: 63679675
  • Language: English
  • Registered On: April 29, 2016, 9:23 am
  • Number of Articles: 4454
  • Latest Snapshot: May 11, 2025, 12:12 pm
  • RSS URL: http://borncity.com/win/category/windows/feed
  • Publisher: https://borncity.com/win
  • Description: Android, Linux, iOS, Windows, Gagdets and more Geek stuff
  • Catalog: //windows14882.rssing.com/catalog.php?indx=63679675
Remove ADS
Viewing all 4454 articles
Browse latest View live
↧

Windows 10 Insider Preview Build 18836 (20H1) released

February 14, 2019, 1:42 pm
≫ Next: Tip: New Windows 7 SP1 ISOs install image downloadable
≪ Previous: Microsoft Patchday: Other Updates February 12, 2019
$
0
0

Microsoft has just released Windows 10 Insider Preview Build 18836 in Skip Ahead ring. This is a build within the 20H1 development branch – should end in the Spring 2020 Windows, something that should come out in a year.

Currently we’re testing the previews from the 19H1 development branch and sometime in the near future we’ll have previews from the 19H2 development branch for the ‘Fall 2019 Windows 10’. At first I believed in a typo that Dona Sakar made in her tweet:

Hello #WindowsInsiders we have released 20H1 Build 18836 to those of you who opted into Skip Ahead: https://t.co/JAkQYVHVyX

— Dona @ #MSIgniteTheTour (@donasarkar) 14. Februar 2019

But when I compared the build numbers (currently the Insider Preview 18334 from the 19H1 development branch is available in the Fast Ring, I realised that they released a build from an development branch that will end 2020 in a Windows 10 feature update. Thought ‘What they are smoking in Redmond’ – and it seems that I’m not alone.

Such an approach when WindowsInsiders receive builds from 2 different dev. branches 19H2/20H1 will discourage users from installing intermediate #SAC releases, and this will not improve the quality of releases, WindowsInsiders who want to test builds will become less with time!

— WZor (@WZorNET) 14. Februar 2019

The announcement of the new Insider Preview Build 18836 from the 20H1 development branch can be found in the Windows Blog.

Hello Windows Insiders, today we are releasing a new build to Insiders who have opted into Skip Ahead. These builds are from the 20H1 development branch. Some things we are working on in 20H1 require a longer lead time. We will begin releasing 19H2 bits to Insiders later this spring after we get 19H1 nearly finished and ready; once 19H1 is “nearly finished and ready” we’ll also use the Release Preview ring for previews of drivers and quality updates on 19H1.

Who the heck is eager to test this 20H1 Insider Preview build? What I’m missing here?

↧
Search

Tip: New Windows 7 SP1 ISOs install image downloadable

February 14, 2019, 3:11 pm
≫ Next: Windows 10: SAC-T is dead for Windows Update for Business
≪ Previous: Windows 10 Insider Preview Build 18836 (20H1) released
$
0
0

win7Microsoft has created new ISO files of Windows 7 SP1 (Build 7601.24214.180801) and offers them for download. They are 64-bit versions of Home Premium, Professional and Ultimate.

WalkingCat (@h0x0d) noticed this and posted the download links for Windows 7 ISO build 7601.24214.180801-1700.win7sp1_ldr_escrow within the following tweet. 

Windows 7 ISOs, build 7601.24214.180801-1700.win7sp1_ldr_escrow Ultimate x64 https://t.co/vhHURTE6gC Professional x64 https://t.co/IeohdVqMv0 HomePremium x64 https://t.co/VQ1dqvn6BW

— WalkingCat (@h0x0d) 14. Februar 2019

This is interesting, because no Windows 7 SP1 ISOs can currently be downloaded from the Adguard website (‘Download is not available’).

Windows 7 Ultimate x64
Windows 7 Professional x64
Windows 7 HomePremium x64

↧
↧

Windows 10: SAC-T is dead for Windows Update for Business

February 15, 2019, 2:10 am
≫ Next: MSIX Packaging Tool January 2019 release available
≪ Previous: Tip: New Windows 7 SP1 ISOs install image downloadable
$
0
0

[German]Microsoft has just declared the Semi Annual Channel-Targeted (SAC-T) for enterprise customers ‘as dead’. Starting with Windows 10 V1903, SAC-Tis history. Here is some information on the topic.

The explanations below only apply to corporate customers (who are on the road with Windows 10 Pro or Enterprise or Education). For users of Windows 10 Home there is no change. 

Windows 10 Semi Annual Channel models

First a short review of the classification. Microsoft releases two feature updates per year for Windows 10 clients, one in spring and one in autumn. According to my blog post Windows 10 Support extended to 30 months (sometimes), the spring builds of Windows 10 Enterprise and Windows 10 Education get 18 months of support, while the fall builds get 30 months of support. 

Till now, Windows Update for Business allowed administrators in a corporate environment to control when Windows 10 clients should receive feature updates. For this purpose, administrators assigned the clients under Windows Update for Business to one of the following two categories:

  • Semi Annual Channel-Targeted (SAC-T): This channel stands for ‘Branch Readiness Level’. This means that the client should receive a feature update as soon as possible after a build has been released. In this scenario, Microsoft blocks the rollout of the targets until it is known that they are compatible.
  • Semi Annual Channel (SAC): Semi Annual Channel (SAC): This channel stands for a delayed delivery of feature updates (Deferral). In this variant, an administrator sets a deferral period in days that refer to the release date of a feature update. No feature update is offered to this machine during the delay time.

Update-Einstellungen Windows 10  V1809
(Source: Microsoft)

The screenshot above shows the setting options from (and up to) Windows 10 V1809. In the first variant, administrators could let Microsoft decide when to provide a feature update for the clients. In the second variant, the rollout was delayed until the administrator was ready for the upgrade. And Microsoft announced on its Windows 10 lifecycle website when a feature update is ready for SAC (SAC-Targeted ends then).

SAC-Targeted disappears with the V1903

It has been suggested for some time that the above model of Semi Annual Channel-Targeted (SAC-T) will disappear. Microsoft employee John Wilcox has posted an announcement Windows 10 and the “disappearing” SAC-T on May 31, 2018. But then there was no more details. Now John Wilcox published the article Windows Update for Business and the retirement of SAC-T on February 14, 2019. Wilcox wrote:

Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release.

Update-Einstellungen Windows 10 V1903
(Source: Microsoft)

Administrators who use Windows Update for Business will only see a changed GUI (see image above) in the advanced update settings page. The setting option for SAC or SAC-T is completely omitted. The administrator sees only two settings options to specify the delay time in days for feature updates and quality updates.

Anyone using the System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools will now only receive a feature update for WSUS that is released at the time a feature update is released (so the second feature update, if the build has been declared SAC-ready, is omitted).

What changes for business customers from V1903 onwards?

Wilcox also discusses the (one time) transition of Windows 10 clients, which are in Windows Update for Business, from an older Windows 10 build to version 1903. 

  • Anyone who has set a delay time in SAC-T will be offered the feature update after this time (unless the machine is not yet in the upgrade cycle).
  • Systems classified in the SAC category are receiving an additional delay of 60 days for upgrading to version 1903 (to compensate for approximately 3 months previously estimated for SAC-ready). This is an ‘one time’ action to reach V1903.

    For example, if a device is currently configured to delay the upgrade for 30 days to version 1903 after the SAC release date, 60-day delays will now be added to the configured 30-day delays. (Note that the additional 60 days are handled on the Microsoft Services page and are not reflected in the Windows Update settings in the device configuration.)

For feature updates after version 1903, the shift set by the administrator then applies again.

↧

MSIX Packaging Tool January 2019 release available

February 15, 2019, 3:09 pm
≫ Next: USB install media and ‘Windows Information Protection’
≪ Previous: Windows 10: SAC-T is dead for Windows Update for Business
$
0
0

A brief information for people who distribute MSIX packages in corporate environments. Microsoft has released the January 2019 release of the MSIX Packaging Tool. It now supports Windows 10 V1709 and Windows 10 V1803.

What are MSIX packages and what is the Packaging Tool?

MSIX is the Windows App package format that allows all Windows applications to be packaged for distribution. The MSIX package format preserves the functionality of existing app packages and/or installation files and provides new, advanced packaging and deployment capabilities for Win32, WPF and WinForm applications.

The MSIX Packaging Tool allows you to create MSIX packages from old or new Windows apps. These can then be distributed within an enterprise environment. The MSIX packaging tool is available from the Microsoft Store. Microsoft has provided some information about the tool here. 

January 2019 release of MSIX Packaging Tool

Microsoft releases updated versions of the MSIX Packaging Tool from time to time. In this tweet, the January 2019 version of the tool was announced on February 11, 2019.

An updated version of the MSIX Packaging Tool is now available! Plus, MSIX now supports #Windows10 versions 1709 and 1803 (in addition to 1809). A great way to start the week. Learn more here: https://t.co/qOwPtloNcO pic.twitter.com/0pravHetFE

— Windows IT Pro (@MSWindowsITPro) 11. Februar 2019

The MSIX Packaging Tool is now, according to this Microsoft article, available in version 1.2019.110.0. The tool allows IT professionals (and developers) to update their existing app installers to MSIX. 

At the same time, Microsoft mentions, that it is now possible to distribute MSIX packages to companies with tools such as System Center Configuration Manager (SCCM), Microsoft Intune, PowerShell, double-click file implementations, or install directly from APIs. This change does not include distribution from the Microsoft Store or Microsoft Store for Business that requires Windows 10 1809 or later.

↧

USB install media and ‘Windows Information Protection’

February 16, 2019, 3:59 pm
≫ Next: Windows 10: Update KB4023057 re-released (02/14/2019)
≪ Previous: MSIX Packaging Tool January 2019 release available
$
0
0

[German]There is an interesting article from Microsoft for administrators who frequently create USB installation media in environments where Windows Information Protection (WIP) is enforced. Then WIP intervenes and prevents the USB installation media from booting or the setup from running.

Windows Information Protection (WIP)

Windows Information Protection (WIP) is a feature, available since Windows 10 V1607. WIP addresses the problem that private devices from employees used in organizations increases the risk of accidental data loss from apps and services that are not under corporate control, such as email, social media, and the public cloud. Such data loss occurs when, for example, an employee sends the latest technical drawings to his personal email account, copies and pastes product information into a tweet, or stores an up-to-date sales report in his public cloud repository.

Windows Information Protection (WIP) helps protect against these potential data leaks without impacting employees. Documents are encrypted before they are stored. WIP also protects corporate apps and data on corporate and personal devices that bring employees to work from accidental data loss. All of this is managed via Microsoft Intune or the System Center Configuration Manager (SCCM) and enforced via policies. Microsoft has published further notes here and here, for example.

USB media and WIP

Administrators who frequently create Windows installation images on USB media may encounter problems in environments that use Windows Information Protection (WIP). Microsoft employee Michael Niehaus points this out in an article and the following tweet.

De-WIP a USB key https://t.co/lIcsC6sk5V

— Michael Niehaus (@mniehaus) 25. Januar 2019

When this USB flash drive is created on a Windows 10 device with WIP policies, the stored files are automatically encrypted, based on their file type. However, this may cause USB media with installation images to stop working. They either won’t boot or won’t be able to run the setup. It comes to the strangest errors like the message “access denied”.

Once files on the USB media are encrypted, they can no longer be used on another computer or in Windows PE. The deactivation of encryption by WIP for the media in question is usually frowned upon for security reasons. 

Assign file ownership ‘Personal’

But the user may overwrite files on the USB device and change them to the status ‘personal’ so that they are decrypted. To do this, select the data in the File Explorer with the right mouse button and select the command “File ownership”-“Personal” in the context menu (see screenshot).

Dateibesitz persönlich
(Source: Microsoft)

Decrypt installation media

Unfortunately, there is no easy way to do this for many subfolders in the File Explorer. The solution comes with the command line tool cipher.exe, which is included in all Windows versions and can decrypt files. The following command decrypts for example all files on the USB medium with the logical drive letter D: 

cipher.exe /d /s:D:\ *.*

After using the command, the files are unencrypted and declared as personnel.

↧
↧

Windows 10: Update KB4023057 re-released (02/14/2019)

February 17, 2019, 12:33 pm
≫ Next: SHA-2 patch for Windows 7 arrives on March 2019
≪ Previous: USB install media and ‘Windows Information Protection’
$
0
0

[German]Brief information for Windows 10 users: Microsoft has re-released its reliability update KB4023057 for Windows 10 (versions 1507 through 1803) on February 14, 2019.

What is Update KB4023057 for?

Update KB4023057, titled ‘Update to Windows 10, versions 1507, 1511, 1607, 1703, 1709 and 1803 for update reliability’, is cyclically rolled out by Microsoft. It is available for Windows 10 V1507 (RTM version) up to version 1803 (but not for the current version 1809). Microsoft writes within the KB article on the update that this brings improvements in the reliability of the Windows Update service.

This update includes reliability improvements to Windows Update Service components in Windows 10, versions 1507, 1511, 1607, 1703, 1709, and 1803. It may also take steps to free up disk space on your device if you do not have enough disk space to install Windows updates.

This update includes files and resources that address issues that affect the update processes in Windows 10 that may prevent important Windows updates from being installed. These improvements help make sure that updates are installed seamlessly on your device, and they help improve the reliability and security of devices that are running Windows 10.

This is in fact the same text as for the September and December 2018 releases. So Microsoft leaves its users pretty much in the dark as to what exactly is to be improved in reliability

Available via Windows Update

The update is only available via Windows Update, i.e. no download from the Microsoft Update Catalog or distribution via WSUS. Can also be interpreted in this way: Business users with WSUS & Co. won’t get this update – Windows 10 Home users are ‘guinea pigs’. Microsoft is testing the stuff on private customers and in small companies with individual Windows 10 Pro computers. Woody Leonhard also has a few words on the update at askwoody.com.

The update is causing issues

The update deeply interferes with the existing Windows 10 installation, cleans user-set update blockers, creates free disk space on the system drive if necessary, resets the network connection and more. More details may be found in my blog post Windows 10: Update KB4023057 released (Sept. 6, 2018). Within my blog post Windows 10: Update KB4023057 released (Dec. 7, 2018) I also gave some hints that this update (at least in some variants) will be installed as an app.

KB4023057-Installation als App

Among other things, it causes people who have blocked the update to get it anyway – see my article for more details. In this article I also touched on some of the problems that users have experienced in the past when installing the update.

Update drops error 0x80070643

The colleagues from deskmodder.der mention in the article here that users who have already installed older versions of the update may receive the error code 0x80070643 (ERROR_INSTALL_FAILURE, Serious installation error) when reinstalling. The error also occurs in previous releases of this update in the forums (e.g. here and here). Remedy should be to uninstall the existing update and restart the system. Addendum: Within my German blog I got some user feedback, that uninstalling the update and rebooting fixed error 0x80070643.

Similar articles:
Windows 10: Update KB4023057 released (Dec. 7, 2018)
Windows 10 reliability update KB4023057 (02/08/2018)
Windows 10: Update KB4023057 re-released
Windows 10 Updates KB4295110/KB4023057 (08/09/2018)
Windows 10: Update KB4023057
Windows 10: What is REMSH.exe for?
Windows 10: Update KB4023057 released (Sept. 6, 2018)
Windows 10: What are Rempl.exe, Remsh.exe, WaaSMedic.exe?
Windows 10: Update KB4023057 re-released (01/16/2019)

↧

SHA-2 patch for Windows 7 arrives on March 2019

February 17, 2019, 3:18 pm
≫ Next: Hotfix KB4465865 for SCCM V1806 Update load issues
≪ Previous: Windows 10: Update KB4023057 re-released (02/14/2019)
$
0
0

win7[German]A brief information for users of Windows 7 and the server pendants. Microsoft will release a critical standalone security update for Windows 7 and Windows Server 2008 / R2 in March 2019, which upgrades these operating systems for SHA-2 support. Here some information about what it is about and when exactly what happens.

What exactly is the SHA-2 topic?

Users of Windows 7 SP1 (and its server counterparts) and WSUS will need a special update from April 2019 onwards. This which will enable the machine to handle SHA2 code signatures in update packages. Without this update, these machines can no longer process updates.

The reason for this is the fact that signing updates with SHA-1 hash values has not been considered secure since a while. Microsoft will therefore discontinue signing update packages with SHA-1 and SHA-2 from July 2019 onward. Microsoft will only provide updates signed with SHA-2. While SHA-2 support is available from Windows 8.1, it is missing in Windows 7 and Windows Server 2008 /R2.

Customers using Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2 (and WSUS 30. SP2) must have SHA-2 code signing support installed on these systems by April 2019. Windows systems without SHA-2 support will no longer be eligible for Windows updates from April 2019. 

I had blogged about that (with more details) in November 2018 within my blog post Windows 7: From April 2019 ‘SHA-2-Support’ is required. However, Microsoft has not provided details and a timetable for the Windows 7 update in November 2018.

A security update will be released in March 2019

Since the February 2019 updates contained nothing of the kind, there is not much time left. User @abbodi86 has now noticed that Microsoft has extended its KB article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS on February 16, 2019 with concrete dates. Here are the details:

Target Date Event Applies To
March 12, 2019 Stand Alone updates that introduce SHA-2 code sign support will be released as security updates. Windows 7 SP1,
Windows Server 2008 R2 SP1.
March 12, 2019 Stand Alone update will be delivered to WSUS 3.0 SP2 that will support delivering SHA-2 signed updates. For those customers using WSUS 3.0 SP2, this update should be installed no later than June 18, 2019. WSUS 3.0 SP2
April 9, 2019 Stand Alone updates that introduce SHA-2 code sign support will be released as security updates. Windows Server 2008 SP2.
June 18, 2019 Windows 10 updates signatures changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone. Windows 10 1709,
Windows 10 1803,
Windows 10 1809,
Windows Server 2019

June 18, 2019

Required: For those customers using WSUS 3.0 SP2, the updates should installed by this date. WSUS 3.0 SP2
July 16, 2019 Required: Updates for legacy Windows versions will require that SHA-2 code signing support be installed. The support released in March and April will be required in order to continue to receive updates on these versions of Windows. Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2.
July 16, 2019 Windows 10 updates signatures changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone. Windows 10 1507,
Windows 10 1607,
Windows 10 1703
August 13, 2019 Contents of updates for legacy Windows versions will be SHA2 signed (embed signed binaries and catalogs). No customer action is expected for this milestone. Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2.
September 16, 2019 Legacy Windows updates signatures  changed from dual signed (SHA1/SHA2) to SHA2 only. No customer action is expected for this milestone. Windows 7 SP1,
Windows Server 2008 R2 SP1,
Windows Server 2008 SP2,
Windows Server 2012,
Windows 8.1,
Windows Server 2012 R2

Customers using WSUS 3.0 SP2 are encouraged to update their servers with the SHA2 updates for WSUS 3.0 SP2 by June 18, 2019. This is the only way to ensure that SHA2-signed updates can be distributed. (via)

↧

Hotfix KB4465865 for SCCM V1806 Update load issues

February 17, 2019, 3:50 pm
≫ Next: Windows 10: update curiosities
≪ Previous: SHA-2 patch for Windows 7 arrives on March 2019
$
0
0

Windows Update[German]Today, a brief post for administrators who use System Center Configuration Manager 1806 and have issues that updates are not loading when WSUS is disconnected. Microsoft has released a KB4465865 hotfix to fix certain issues.

I came across the subject through a tweet by MVP Jean-Sébastien. He described the whole thing in his Frensh blog within the article [SCCM 1806] Software Updates Do Not Download If WSUS Is Disconnected.

[SCCM 1806] Les mises à jour logicielles ne se téléchargent pas si WSUS est déconnecté J’étais passé à côté de ce correctif (KB4465865) à destination de System Center Configuration Manager 1806 mais qui a toute son importance ! Ce dernier corrige plusie… https://t.co/6Os4dLm12X

— Jean-Sébastien (@microsofttouch) 11. Februar 2019

It is about the System Center Configuration Manager 1806, which requires the hotfix KB4465865. This patch fixes several issues with software updates when you use Express Updates. The patch has been available directly from the SCCM console since mid-October 2018 and should be installed immediately.

Microsoft has described in article KB4465865 (Software updates do not download in Configuration Manager environment if WSUS is disconnected) what the hotfix is supposed to fix.

↧
Search

Windows 10: update curiosities

February 18, 2019, 9:53 pm
≫ Next: Windows Server 2016: Empirical proof of slow Update installs
≪ Previous: Hotfix KB4465865 for SCCM V1806 Update load issues
$
0
0

[German]Windows 10 comes with some Windows Update curiosities. It makes a difference whether updates are offered automatically or whether they are obtained via update search. And you can also deactivate the search for updates button.

Don’t search for Windows 10 Updates!

I was aware of, but didn’t discuss it here within my blogs: But in December 2018 Chris Hoffman from howtogeek.com had written an article about a curiosity.

Here we go again: Clicking “Check for Updates” still installs unstable updates on Windows 10. Microsoft confirmed this in a blog post yesterday. https://t.co/pVnwCNY3lu

— Chris Hoffman (@chrisbhoffman) 11. Dezember 2018

The beef is that Windows 10 automatically checks for updates, downloads them and then offers them for installation. With this automatic update search, only important updates are found and offered (see following figure from a German Windows 10). 

In Windows 10 Home you can’t control, when and what update will be installed. But a user can also check for updates in the Windows 10 Update & security settings category Windows Update. To do this, click the Check for Updates button (shown below).

Windows 10: Update search

Windows 10 starts a search for pending updates. This search finds important updates, as well as optional updates provided by Microsoft as previews or early feature updates, and offers them for installation.

The problem with this approach

For Windows 10 V1809 (October 2018 update), ‘experienced’ users were able to install this version early via an update search. The consequences are known: Numerous users ran into serious issues, so that Microsoft suspended this functional update and only released it again after weeks.

Chris Hoffman had published this article at howtogeek.com, which says: If users click on the update search, they endanger the stability of Windows 10. Hoffman’s claim was based on a blog post by Michael Fortin, Corporate Vice President for Windows at Microsoft. Fortin explained that there are security and quality updates from Microsoft for Windows 10 and discusses update types.

Security updates that are delivered on the 2nd Tuesday of the month (Patchday) are so-called B release updates. These are found by the automatic update search. However, there are also optional updates, which are rolled out as C and D releases in the third and fourth week. According to Fortin, these are updates that are delivered to commercial corporate users and ‘advanced’ users when searching for updates. 

We also release optional updates in the third and fourth weeks of the month, respectively known as “C” and “D” releases. These are validated, production-quality optional releases, primarily for commercial customers and advanced users “seeking” updates. These updates have only non-security fixes. The intent of these releases is to provide visibility into, and enable testing of, the non-security fixes that will be included in the next Update Tuesday release.

The above text snippet from this blog post shows the problem: The C- and D-Releases updates, which are found during an update search, should give experienced users and enterprise administrators the possibility to test preview updates. These updates will be shipped within the following month’s the regular security update, which is automatically found and installed. So

If you use the update search to search for new updates, you are at risk to run into trouble. Whenever Microsoft delivers faulty updates, people who use the search for updates will run into issues. Here in the blog there are some documented cases (e.g. BlueScreens at Surface Book 2 through updates). If you let Windows 10 do its work, you won’t see these updates. Microsoft often fixed the bugs, before shipping an update at the ‘next months’ patchday.

Tip: Disable Update search

German blog reader Markus K. (thanks for that) had me already alerted me in October 2018 with a short message I found the following interesting link … Finally one seems to be able to actually stop the update search! I’m sure you’re looking forward to this Japanese Microsoft website with a blog post by the Microsoft WSUS team. The post is about the manual update search in Windows 10, which can be triggered in the settings (see above explanations). The message of the article:

If the updates are distributed via WSUS, the update search also triggers the download of optional updates. Now there may be a desire in an organization to prevent this manual update search via group policy. This can be done in the Group Policy Editor within the branch:

Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update

There you have to activate the policy Remove Access to All Windows Update Features. Under Windows 10 Home, the Registry Editor could be used with administrative permissions to set a DWORD value. Navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

and set the DWORD 32 bit value SetDisableUXWUAccess to 1, to activate the policy. Then the Check for Updates button is blocked and is no longer available for users. 

Windows 10: blocked update search

It looks then similar to the (German) screenshot above. The user is notified that this option is ‘managed by your organization’ – it is disabled by Group Policy.

User complaint: Windows update doesn’t find everything

A few days ago blog reader Marco M. contacted me with an observation about the Windows 10 update and asked if I knew of the following ‘anomaly’. 

Maybe you’ve noticed something similar about yourself before. Detached whether VM, fat client, same subnet / gateway, 1803, 1809, Windows 10 Pro/Home, with / without domain / standard update GPO etc.

The system has been running for days or has just started. In the update settings page it says, “last searched at XX o’clock – you are up to date”.

This can be already 5 minutes ago or 1-2 hours ago. If you manually let Windows 10 search for updates again, updates will be found and installed.

What could be the reason for this? Do you already have similar experiences?

I had mentioned the problem of B, C and D updates described above within my answer and claim C and D updates, that will be found during a manual update search. Marco M answered:

In fact, these could be optional updates. If the definition of waves is similar to how smartphone updates distribute which OTA (one gets it now, the other later), I agree.

But then Marco mentioned that he has different systems that will probably find different updates. Marco wrote:

The behavior occurs, for example, in two systems, identical in hardware. Same subnet, identical gateway.

So if two Windows 10 systems find different updates during the search, it will be difficult to explain- the above remarks are no longer fit. And different hardware that could explain the different updates does not apply to ‘identical machines’ either.

Another observed problem

Marco described  in a follow-up mail another problem in Windows domains, which might be interesting for domain admins.

When we talk about updates, I still have another observation, which is located within a Windows domain. .

In Win7 Pro the update distribution was reliable. 2016 Domain – current GPOs (newly created with 2016) – current 2016 WSUS Server

Update settings

The systems automatically checked for [updates] at intervals – [and] downloaded those. In the start menu there was the info “Restart and install” or “Shutdown and install”. With Windows 10 it doesn’t work anymore. The display remains unchanged (see below).

 Start menu shudown options

First you have to set the options to search for updates via Settings -> Update and Security. Then the user gets the possibility as described above. I’ve set the GPO as shown below, without success.

Update GPO settings

The last option is to define “Install daily – 12 o’clock” all updates.

Update settings (GPO)

It is unfortunate that with some Outlook updates the system need to be restarted because (in combination [with] Exchange) the information store (.ost file) is not available.

Unfortunately, our employees are not happy about system updates with associated restarts.

Until now the “Install & Shutdown” at the end of the day was the best solution. January 2020 is approaching and Windows 10 is becoming more and more a topic.

What is your opinion about that issues? Can you confirm what Marco wrote? Are there other GPOs that could be used?

Similar articles:
Windows 10 V1809: Available via update search
Surface Book 2: Update KB4467682 causes blue screens …

↧
↧

Windows Server 2016: Empirical proof of slow Update installs

February 19, 2019, 3:57 pm
≫ Next: Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)
≪ Previous: Windows 10: update curiosities
$
0
0

[German]Administrators of Windows Server 2016 systems have been plagued by very slow update installation since the release of this operating system. Now I have empirical test data showing how lame the server are when installing updates – compared with Windows Server 2019. And Windows 10 V1607 LTSC clients are probably affected in the same way.

What exactly is this about?

In forums such as Microsoft’s Answers, frustrated administrators have been complaining for some time about the extremely slow update installs on Windows Server 2016 (LTSC). In this Technet thread a user called it a nightmare, and in Microsoft’s User Voice there are two entries here and here that complain about an update installation speed problem. If updates are installed, the server will be down for hours at the required restart, or it will be idled with the display ‘Windows is being prepared …’. 

An unacceptable situation for administrators. Some of them are now shifting update installations to the weekend so that company employees can work during the week. While Apple’s says ‘It just works’, IT admins in the Microsoft universe have to spend their weekends trying to keep the stuff running.

Detailed description in the Technet forum

This Technet thread from July 2017 describes the administrators’ dilemma quite precisely: A customer of the Thread Starter runs a number of Windows servers, ranging from Windows Server 2008 R2, through Windows Server 2012 / R2 to Windows Server 2016. It is noticeable that Windows Server 2016 is extremely slow when installing updates. While the older Windows Server variants are ready with an update installation after an hour, the administrator in question writes, the machines with Windows Server 2016 sometimes needs one day for updates until they are operational again. A no go in my opinion.

A survey shows the dissatisfaction

I had addressed this issue in summer of 2018 within my blog post Windows Server 2016: Slow updates. Some user comments confirmed that observation.


(Source: Survey on Borncity)

A few weeks later I started a poll (see Survey: Slow Windows Server 2016 Update installs?) on this topic here within my blog. In the survey with 436 participants 96% confirmed a slow update installation (see graphic above). However, the sample size of the participants is quite small.

An empirical analysis

Blog reader Karl has now given me the results of an empirical study he carried out on the subject. He measured the individual times for download, installation and restart as well as the total time for the update installation. The following tweet already shows the trend:

@MSFTtoday @windowsserver I expect this post will be unpopular but please finally hear the uservoice and fix Server 2016 LTSC soon™
Updates 02-2019 + .net Server 2019 LTSC 4 mins 50 sec
Updates 02-2019 Server 2016 LTSC 44 mins 28 sec #servers
Onedrivehttps://t.co/OFDcf4hKD0

— al Qamar (Karl) (@tweet_alqamar) 16. Februar 2019

The following table shows the results of various measurements for Windows Server 2016 LTSC Core and Windows Server 2016 LTSC GUI test machines compared to their Windows Server 2019 counterparts. 

 

Search Updates

Download*

Install

Restart / Apply / Logon

Total Time (roughly)

Server 2019 LTSC Core

3s

11s 2m32s 45s 3m56s

Server 2016 LTSC Core

13s

*13m 44s

*6m 8s

2m 57s

23m 26s

Server 2019 LTSC GUI

4s

21s

3m 16s

52s

4m 40s

Server 2016 LTSC GUI

25s

*22m 10s

*7m 20s

14m 50s

44m 28s

*Remarks: Due to a bug in 1607 download and install phase are wrong (fixed in Server SAC / Client 1703 and later), the DL is finished but it changes to install phase later while tiworker is already running. A 450 mbit line is not the bottleneck to DL patches from WU. So install time cannot measured well and needs to be seen additive.

Karl wrote in his mail that he had difficulties to stop the time within the GUI and in the core server exactly. But this should not be the subject of a discussion – it’s about the trend. And the table above sends a clear message. 


(Source: Borncity.com)

I have created the above diagram to compare the measured total times for the update installation on the test machines. The installation times for updates on Windows Server 2016 are a disaster. In Windows Server 2019 LTSC Core and GUI the updates are installed after less than 5 minutes, the server is ready for use again. With Windows Server 2016 LTSC Core and GUI, the administrator waits between 24 minutes to 44 minutes until the machine is back for operation.

This behavior from Windows Server 2016 LTSC also applies to the Windows 10 V1607 LTSC clients.

Don’t use Windows Server 2016 LTSC!

Karl told me, that he helps customers as an IT consultant migrate from Windows 7 or Windows Server 2008 R2 to newer products such as Windows 10 and Windows Server 2016/2019. His verdict: “With the current developments in Windows 10 and Windows Server, the LTSC branches (clients and servers alike) causes more problems than their design can solve.” He told me: 

I have come to the point of abandoning the recommendation of Server 2016 completely for our customers. I recommend going straight to Windows Server 2019, because Microsoft’s LTSC approach simply doesn’t work as intended.

Microsoft now wants customers to update to the latest version whenever possible, whether it’s a server or a client. In other words: Redmond has screwed it up, it won’t be fixed anymore and the customer is once again on the ‘dead end’. Because updating a Windows Server 2016 LTSC without software assurance and volume license agreement to the 2019 version will be expensive. Thanks to Karl for the information and the data. 

Similar articles:
Windows Server 2016: Slow updates
Survey: Slow Windows Server 2016 Update installs?
Stuipd idea using Windows 10 LTSC or tinkering with V1607

↧

Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)

February 20, 2019, 12:55 am
≫ Next: Windows 10 Updates (Feb. 19, 2019)
≪ Previous: Windows Server 2016: Empirical proof of slow Update installs
$
0
0

Windows Update[German]On February 19, 2019, Microsoft released a Preview Rollup Update KB4486565 for Windows 7 and Windows Server 2008 R2 SP1. At the same time a Preview Rollup Update KB4487016 for Windows 8.1 and Windows Server 2012 R2 was released.

Preview Rollup Updates are optional, quasi for testing, their content will be released on the following regular patchday.

Updates for Windows 7/Windows Server 2008 R2

A preview rollup update has been released for Windows 7 SP1 and Windows Server 2008 R2 SP1. The update history for Windows 7 can be found on this Microsoft page.

KB4486565 (Preview Monthly Rollup) Windows 7/Windows Server 2008 R2

Update KB4486565 (Preview Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1) contains improvements and bug fixes to be rolled out next month. The update addresses the following:

  • Updates time zone information for Chile.
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows.
  • Adds support for the SignerSignEx2 API to allow Windows Server Update Services 3.0 SP2 to sign files using this API.
  • Addresses an issue that can overwrite gan-nen support behavior for the Japanese era with a newer update. For more information, see KB4469068.
  • Enables the 元年 character for the first year in the Japanese era. For more information, see KB4469068.
  • Addresses an issue that fails to display the correct Japanese era name in Microsoft Office Visual Basic for Applications. For more information, see KB4469068.
  • Addresses an issue that fails to recognize the first character as the abbreviation for the Japanese era name. For more information, see KB4469068.
  • Addresses an issue that may cause virtual machines (VM) to fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

The update is automatically downloaded and installed by Windows Update. It can also be downloaded from the Microsoft Update Catalog. Microsoft strongly recommends that you install the latest Service Stack Update (SSU) KB3177467 before installing the latest rollup. With Windows Update, the SSU is automatically offered before the installation. Since this is a preview rollup, I would hide KB4467108.

The preview rollup update addresses the Microsoft Jet database error and a bug in VMs. But there are two known issues:

Symptom Workaround
After installing this update, the Event Viewer may not show some event descriptions for network interface cards (NIC). Currently, there is no workaround for this issue.

Microsoft is working on a resolution and estimates a solution will be available in March 2019.

After installing this update, Internet Explorer 11 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./li>
  • 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.

Updates for Windows 8.1/Windows Server 2012 R2

A preview rollup update has been released for Windows 8.1 and Windows Server 2012 R2. The update history for Windows 8.1 can be found on this website.

KB4487016 (Preview Monthly Rollup) Windows 8.1/Windows Server 2012 R2

Update KB4487016 is available for Windows 8.1 and Windows Server 2012 R2 as Preview of Monthly Rollup. This is not a security update. The preview rollup addresses the following items:

  • Updates time zone information for Chile.
  • 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 reliability issues for the Virtual Machine Management Service (VMMS) during live migration.
  • Addresses an issue that may cause a server to stop working when handling a compound client request that includes a rename.
  • Addresses an issue that may cause an error at Stop 24 on a virtual Remote Desktop Services (RDS) server.
  • Addresses an issue that causes the clock and the calendar flyout to ignore user settings for Japanese Era date and time formats. For more information, see KB4469068.
  • Addresses an issue that can overwrite gan-nen support behavior for the Japanese Era with a newer update. For more information, see KB4469068.
  • Enables the 元年 character for the first year in the Japanese Era. For more information, see KB4469068.
  • Addresses an issue that fails to display the correct Japanese Era name in Microsoft Office Visual Basic for Applications. For more information, see KB4469068.
  • Addresses an issue that fails to recognize the first character as the abbreviation for the Japanese Era name. For more information, see KB4469068.
  • Enables users to review location settings.
  • Addresses an issue that may cause virtual machines (VM) to fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).” This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

Microsoft tries again to patch the Japanese calendar (Microsoft has been working on it since Nov. 2018). The update is automatically downloaded and installed by Windows Update. It can also be downloaded from the Microsoft Update Catalog. But IE 11 has the following known problem with user authentication::

After installing this update, Internet Explorer 11 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./li>
  • 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.

Since this is a preview rollup, I would hide KB4467108. The only interesting thing for some affected users might be Microsoft’s attempt to fix the broken Microsoft Jet database engine and the problems with virtual machines.

Similar articles:
Microsoft Office Patchday (February 5, 2019)
Flash Player 32.0.0.142 released
Microsoft Security Update Summary (February 12, 2019)
Patchday: Updates for Windows 7/8.1/Server 12. Feb. 2019
Patchday Windows 10 Updates (February 12, 2019)
Patchday Microsoft Office Updates ( February 12, 2019)
Microsoft Patchday: Other Updates February 12, 2019

Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)
Windows 10 Updates (Feb. 19, 2019)

↧

Windows 10 Updates (Feb. 19, 2019)

February 20, 2019, 1:43 am
≫ Next: Windows 10 Insider Preview Build 18342
≪ Previous: Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)
$
0
0

[German]On February 19, 2019, Microsoft released several cumulative updates for Windows 10. All updates are optional – here is an overview of these cumulative update packages.

The information can be found in the Windows 10 Update History page. Please note that support for older Windows 10 versions has expired. Windows 10 Home and Windows 10 Pro will then no longer receive updates. 

Update KB4487029 for Windows 10 V1803

Cumulative Update KB4487029 for Windows 10 V1803 raises the build to 17134,619. The update includes quality improvements, but no new operating system features. Here is the list of changes:

  • Enables media content to play e-learning content with plug and play USB adapter cables on Microsoft Edge. 
  • Ensures that windowed ActiveX content inside an iframe scrolls along with other page content in Internet Explorer 11 during a user-triggered scroll operation. 
  • Addresses an issue that causes app-specific registry keys to be deleted after updating an application. 
  • Updates time zone information for Chile. 
  • Addresses an audio compatibility issue when playing newer games with 3D Spatial Audio mode enabled through multichannel audio devices or Windows Sonic for Headphones. 
  • Addresses an issue that prevents some users from pinning a web link to the Startmenu or the taskbar. 
  • Addresses an issue in which the desktop lock screen image set by a group policy will not update if the image is older than or has the same name as the previous image. 
  • Improves performance related to case-insensitive string comparison functions such as _stricmp() in the Universal C runtime. 
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows. 
  • Improves the reliability of the UE-VAppmonitor. 
  • Addresses an issue that fails to update a user hive when you publish an optional package in a Connection Group after the Connection Group was previously published.  
  • Addresses an issue that allows files protected by Windows Information Protection to be transferred using Bluetooth to an unmanaged machine. 
  • Addresses an issue that occurs with the Internet Explorer proxy setting and the out of box experience (OOBE) setup. The initial logon stops responding after Sysprep. 
  • Addresses an issue that prevents a user from deleting a wireless network profile in some scenarios. 
  • Addresses an issue that may cause a “STOP 0x1A” error when you use certain applications or log in or log out of a system.
  • Addresses an issue in the Timeline feature that causes File Explorer to stop working for some users.
  • Addresses an issue that causes the Photos app to stop working when it’s used from the Mail app.
  • Addresses an issue in the PLMDebug.exe tool that loses debug sessions when used with a Universal Windows Platform (UWP) app.
  • Improves Always On VPN (AOVPN) reconnect and disconnect functionality.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

This optional update will only be offered if the user explicitly requests the search for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. Please make sure that the latest Servicing Stack Update (SSU) KB4485449 is installed. Microsoft is currently not aware of any issues with this update.

Update KB4487021 for Windows 10 V1709

Cumulative Update KB4487021 for Windows 10 V1709 raises the build to 16299.1004. The update includes quality improvements, but no new operating system features. Here is the list of changes: 

  • Updates time zone information for Chile. 
  • Improves performance related to case-insensitive string comparison functions such as _stricmp() in the Universal C runtime. 
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows. 
  • Improves the reliability of the UE-VAppmonitor. 
  • Addresses an issue that fails to update a user hive when you publish an optional package in a Connection Group after the Connection Group was previously published.
  • Adds a new group policy called “Policy Details”. This policy will immediately disconnect any wireless connections when a wired connection is detected and “Minimize simultaneous connections” is configured.
  • Addresses an issue that causes the clock and the calendar flyout to ignore user settings for Japanese era date and time formats. For more information, see KB4469068.
  • Addresses an issue that can overwrite gan-nen support behavior for the Japanese era with a newer update. For more information, see KB4469068.
  • Enables the 元年 character for the first year in the Japanese era. For more information, see KB4469068.
  • Addresses an issue that fails to display the correct Japanese era name in Microsoft Office Visual Basic for Applications. For more information, see KB4469068.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

This optional update and will only be offered if the user explicitly requests the search for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. Please make sure that the latest Servicing Stack Update (SSU) KB4470788 is installed. There are currently no known issues with the update. 

Update KB4487011 for Windows 10 V1703

Cumulative Update KB4487011 for Windows 10 V1703 is only available for Windows 10 V1709 Enterprise and Education and raises the build to 15063,1659. The update includes quality improvements, but no new operating system features. Here is the list of changes:

  • Updates time zone information for Chile. 
  • Addresses an issue that causes an application to stop responding when two of its threads share the same input queue. 
  • Addresses an issue with a rooted pointer to an item identifier list (PIDL) in File Explorer. 
  • Improves performance related to case-insensitive string comparison functions such as _stricmp() in the Universal C runtime. 
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows. 
  • Improves the reliability of the UE-VAppmonitor.
  • Addresses an issue that causes the clock and the calendar flyout to ignore user settings for Japanese era date and time formats. For more information, see KB4469068.
  • Addresses an issue that can overwrite gan-nen support behavior for the Japanese era with a newer update. For more information, see KB4469068.
  • Enables the 元年 character for the first year in the Japanese era. For more information, see KB4469068.
  • Addresses an issue that fails to display the correct Japanese era name in Microsoft Office Visual Basic for Applications. For more information, see KB4469068.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

This optional update will only be offered if the user explicitly requests the search for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. Please make sure that the latest Servicing Stack Update (SSU) KB4487327 is installed. There are currently no known problems with the update.

Microsoft simultaneously updates the Update Client with a direct update – see KB article.

Update KB4487006 for Windows 10 V1607

Cumulative Update KB4487006 for Windows 10 V1607 is only available for Enterprise und Education – and for machines with Clovertrail chipset. Itaises the build to 14393.2828. The update includes quality improvements, but no new operating system features. Here is the list of changes:

  • Updates time zone information for Chile. 
  • Addresses an issue that may cause the Remote Desktop Protocol (RDP) client application to display a black screen at user login. 
  • Improves performance related to case-insensitive string comparison functions such as _stricmp() in the Universal C runtime. 
  • Addresses an issue with evaluating the compatibility status of the Windows ecosystem to help ensure application and device compatibility for all updates to Windows. 
  • Improves the reliability of the UE-VAppmonitor. 
  • Addresses an issue with the display of user names in the Routing and Remote Access Service (RRAS) servers. 
  • Addresses an issue that causes updates to a relying party trust to fail when using PowerShell or the Active Directory Federation Services (AD FS) management console. This issue occurs if you configure a relying party trust to use an online metadata URL that publishes more than one PassiveRequestorEndpoint. The error is, “MSIS7615: The trusted endpoints specified in a relying party trust must be unique for that relying party trust.” 
  • Addresses an issue that displays a specific error message for external complexity password changes because of Azure Password Protection policies. 
  • Addresses an issue that may cause Microsoft Outlook to display the error, “The operation failed” when viewing the Microsoft Exchange Address Book. This issue occurs after installing KB4457127 on Active Directory domain controllers that utilize Microsoft Exchange. The error appears on Microsoft Outlook clients that use locales other than EN-US. 
  • Addresses an issue that may prevent you from enabling Storage Maintenance Mode on timeout if the storage is under load. 
  • Addresses an issue that may cause a server to stop working when handling a compound client request that includes a rename. 
  • Addresses an issue that may cause error “0x165” when you pause a node and take it down for maintenance. 
  • Addresses an issue that may cause an error at Stop 24 on a virtual Remote Desktop Services (RDS) server.
  • Addresses an issue that fails to recognize the first character of the Japanese era name as an abbreviation and may cause date parsing issues.
  • Addresses a reliability issue with win32kfull.sys introduced in KB4487026.
  • Addresses an issue that may prevent Internet Explorer from loading images that have a backslash (\) in their relative source path.
  • Addresses an issue that may cause applications that use a Microsoft Jet database with the Microsoft Access 95 file format to randomly stop working.

This optional update will only be offered if the user explicitly requests the search for updates in the settings page. The update can also be downloaded and installed from the Microsoft Update Catalog. However, it is important to ensure that the latest Servicing Stack Update (SSU) KB4485447 is installed.

Microsoft updates the Update Client at the same time by a direct update – furthermore this update has several known issues. Details can be found in the KB article.

Similar articles:
Microsoft Office Patchday (February 5, 2019)
Flash Player 32.0.0.142 released
Microsoft Security Update Summary (February 12, 2019)
Patchday: Updates for Windows 7/8.1/Server 12. Feb. 2019
Patchday Windows 10 Updates (February 12, 2019)
Patchday Microsoft Office Updates ( February 12, 2019)
Microsoft Patchday: Other Updates February 12, 2019

Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)
Windows 10 Updates (Feb. 19, 2019)

↧

Windows 10 Insider Preview Build 18342

February 20, 2019, 5:28 pm
≫ Next: CCleaner v5.53.7034 available, forced update again?
≪ Previous: Windows 10 Updates (Feb. 19, 2019)
$
0
0

Microsoft just released Windows 10 Insider Preview Build 18342 in Fast Ring. This is the version in the 19H1 development branch that we expect to receive in April 2019 as Windows 10 V1903. 

The announcement and a description of the new features can be found in the Windows Blog. PCs with the following processor model numbers will not receive this build due to a Connected Standby issue: Intel64 Family 6 Model 142 and Intel64 Family 6 Model 158.


(Source: Microsoft)

Microsoft has introduced some improvements in gaming. There is also the chrome extension for Timeline from the Chrome Web Store.

Linux files in the File Explorer

This build also allows users to access Linux files in a WSL distro from Windows. These files can be accessed from the command line, and Windows applications such as File Explorer, VSCode, etc. can also interact with these files. You can read more about this here.

Screenshot of File Explorer showing Linux files.
(Source: Microsoft)

More details about improvments and know issues may be read within the Windows Blog.

↧
↧

CCleaner v5.53.7034 available, forced update again?

February 21, 2019, 1:54 am
≫ Next: Windows 10 V1809 Update KB4482887 as Release Preview
≪ Previous: Windows 10 Insider Preview Build 18342
$
0
0

[English]A brief information for CCleaner users (I know that some of my blog readers are interested in that stuff). Piriform released an update to CCleaner v5.53.7034 for Windows on February 19, 2019.

CCleaner is a free tool to clean up Windows – Wikipedia writes here about ‘optimization’. Some hints on what is ‘cleaned and optimized’ can be found at Askvg. I would quote CCleaner as a kind of snake oil (not really necessary). 

CCleaner
(Source: Talos)

German blog reader Dieter F. sent me a mail about the update (many thanks for that).

What’s new in CCleaner v5.53.7034?

Piriform writes in the release notes that this version includes several improvements and new rules. Here is the list of new features. 

Cleaning Rules
– New cleaning rules for Amazon Music and Amazon Kindle
General
– Increased the default Smart Cleaning notification threshold
– Fixed a crash when running CCleaner alongside Norton AV products
– Fixed a crash in the Professional Trial

Users of the free version of CCleaner must update it manually. The new version of CCleaner Free can be downloaded from this website. CCleaner Professional is updated automatically. CCleaner 5.5x runs under Windows XP, Vista, 7, 8.1 and Windows 10. It is also available as an app for Android.

Forced upgrade again with CCleaner Professional?

According to Piriform, users of CCleaner Professional have the automatic product update activated. However, this option can be deactivated in the settings. German blog reader Dekre left this comment within my German blog, saying:

that the CCleaner, despite deactivation, simply updates itself automatically to the new version.

I assume that he has the CCleaner Professional version, because in the paid version the auto-update is supported. But the user settings should have priority. Blog reader Dekre mentioned also,

that the unchecked option to collect telemetry data is overwritten during upgrade and the option is simply set again.

Dekre mentioned this post from Bleeping Computer, mentions this behavior on September 17, 2018. I’ve have addressed this behavior on Sept. 12, .2018 within my blog post CCleaner forces update from v5.38 to v5.46. Within this article I outlined also some security issues (DLL hijacking) associated with CCleaner).

I generally advise against using the tool. Actually these ‘cleanups’ are superfluous – Windows can do a lot too. In addition, there is always the danger that something will break. Piriform and CCleaner have also attracted attention in the past through a series of unpleasant stories. You can read the details in the following linked articles. So nobody can claim that I didn’t warn.

Similar articles
CCleaner has been infected with malware
CCleaner comes mit AVAST PUP
CCleaner forces update from v5.38 to v5.46
AVAST CCleaner 5.45 and the telemetry thing
CCleaner 5.45 pulled and other peculiarities
CCleaner V 5.46 with improved data settings
CCleaner forces update from v5.38 to v5.46
CCleaner v5.52.6967 released

↧

Windows 10 V1809 Update KB4482887 as Release Preview

February 21, 2019, 2:59 am
≫ Next: Windows 10 V1703 – V1809: Dynamic Updates (Feb. 19/21, 2019)
≪ Previous: CCleaner v5.53.7034 available, forced update again?
$
0
0

Microsoft has released Update KB4482887 for Windows 10 Version 1809 in Release Preview ring. Update KB4482887 raises the OS build to 17763.346, further details are unknown.

↧
Search

Windows 10 V1703 – V1809: Dynamic Updates (Feb. 19/21, 2019)

February 21, 2019, 3:05 pm
≫ Next: Windows 10 V1507 Update KB4491101 (Feb. 21, 2019)
≪ Previous: Windows 10 V1809 Update KB4482887 as Release Preview
$
0
0

[German]Just a brief addendum from this week: On Tuesday, February 19, 2019, Microsoft released the Dynamic Updates KB4486561, KB4486560 and KB4486559 for Windows 10 V1703 to V1803 in addition to various cumulative updates. Addendum: On February 21, 2019, the Dynamic Update KB4482886 for Windows 10 V1809 was also released.

What are Dynamic Updates?

Microsoft has introduced Dynamic Updates to help you dynamically integrate them when you upgrade from an operating system version to a higher version. These dynamic updates are then dynamically reloaded as needed during the installation of Windows 10 (or when a system is reset) in order to include any final fixes that are needed in the system during setup. Microsoft calls these patches Compatibility update for upgrading to Windows 10 and writes:

This update makes improvements to ease the upgrade experience to Windows 10, version xxx.

Such updates contain improvements to facilitate the ‘upgrade experience’. According to this document, critical drivers and enhancements that help upgrade are provided through Dynamic Updates. Dynamic Updates are available through Windows Update and are automatically downloaded and installed. I’ve blogged about that with more details within my blog post Windows 10: What are dynamic updates?

The dynamic updates of February 19, 2019

As of February 19, 2019, Microsoft has released the following compatibility updates for its Windows 10 versions 1703, 1709 and 1803 as dynamic updates:

  • Update KB4486559: Windows 10 Version 1703
  • Update KB4486560: Windows 10 Version 1709
  • Update KB4486561: Windows 10 Version 1803

Details of what these updates really improves are not disclosed by Microsoft. Usually, Microsoft does not make dynamic updates available for download either, since they are downloaded by Microsoft in the latest version during the Windows 10 installation.

If you still need the packages (e.g. for integration into an installation image), you can still download the packages from the Microsoft servers. For version 1703 I found the dynamic update in the Microsoft Update Catalog. The colleagues from German site deskmodder.de have also added download addresses of Microsoft servers here.

On February 21, 2019, the Dynamic Update KB4482886 for Windows 10 V1809 was also released. deskmodder.de has the inofficial downloads.

Similar articles:
Microsoft Office Patchday (February 5, 2019)
Flash Player 32.0.0.142 released
Microsoft Security Update Summary (February 12, 2019)
Patchday: Updates for Windows 7/8.1/Server 12. Feb. 2019
Patchday Windows 10 Updates (February 12, 2019)
Patchday Microsoft Office Updates ( February 12, 2019)
Microsoft Patchday: Other Updates February 12, 2019

Windows 7/8.1 Preview Rollup Updates (Feb. 19, 2019)
Windows 10 Updates (Feb. 19, 2019)

Windows 10: What are dynamic updates?

Windows 7/8.1 Preview Rollup Updates (19. Feb. 2019)
Windows 10 Updates (19. Feb. 2019)

↧

Windows 10 V1507 Update KB4491101 (Feb. 21, 2019)

February 21, 2019, 3:50 pm
≫ Next: Windows 10 Insider Preview Build 18343 (19H1) in Fast Ring
≪ Previous: Windows 10 V1703 – V1809: Dynamic Updates (Feb. 19/21, 2019)
$
0
0

Microsoft released the cumulative update KB4491101 for Windows 10 V1507 on February 21, 2019. This is the RTM version of Windows 10, and the update for the LTSC version is available for download. I have added the details to the article Windows 10 Updates (Feb. 19/21, 2019).

↧
↧

Windows 10 Insider Preview Build 18343 (19H1) in Fast Ring

February 23, 2019, 1:45 am
≫ Next: Windows 10 Insider Preview Build 18841 (20H1) in Skip Ahead
≪ Previous: Windows 10 V1507 Update KB4491101 (Feb. 21, 2019)
$
0
0

Microsoft has published the Windows 10 Insider Preview Build 18343 in the Fast Ring. This is the version in the 19H1 development branch that we expect to receive in April 2019 as Windows 10 V1903.

The announcement and a description of the changes can be found in the Windows Blog. Not much has been changed. 

  • A problem with Connected Standby has been fixed. This caused Microsoft to block PCs with the Intel64 Family 6 Model 142 and Intel64 Family 6 Model 158 processor models. 
  • The problem that required an additional reboot when the PC was reset and My Files should be kept on a device with reserved memory enabled has been fixed.

However, there are still the following known issues:

  • Launching games that use anti-cheat software may trigger a bugcheck (GSOD).
  • Creative X-Fi sound cards are not functioning properly. We are partnering with Creative to resolve this issue.
  • We’re continuing to investigate reported issues in the night light space.
  • Some Realtek SD card readers are not functioning properly. We are investigating the issue.
  • In Windows Sandbox, if you try to navigate to the Narrator settings, Settings app crashes.
  • Mouse pointer color might be incorrectly switched to white after signing out and signing back in.
  • We’re investigating reports of the Chinese version of multiple games not working.

Further details can be found within the Windows Blog.

↧

Windows 10 Insider Preview Build 18841 (20H1) in Skip Ahead

February 23, 2019, 2:57 am
≫ Next: Update KB4491113 fixes Internet Explorer Backslash bug
≪ Previous: Windows 10 Insider Preview Build 18343 (19H1) in Fast Ring
$
0
0

Microsoft has also released Windows 10 Insider Preview Build 18841 in Skip Ahead ring. This is a version from 20H1 branch, that will arrive in April 2020. The announcement and details may be found within the Windows Blog.

↧

Update KB4491113 fixes Internet Explorer Backslash bug

February 24, 2019, 3:26 pm
≫ Next: Windows 10: Support for Colorblind people
≪ Previous: Windows 10 Insider Preview Build 18841 (20H1) in Skip Ahead
$
0
0

Windows UpdateMicrosoft has released a cumulative update KB4491113 for Internet Explorer, which fixes the so-called backslash bug in the browser. This came into effect with the February 2019 updates in Windows 7-10.

The IE Backslash bug

The security updates from February 2019 for Windows 7 SP1 and Windows 8.1 as well as Windows 10 and their server counterparts caused an error in Internet Explorer 11. I didn’t explicitly mention it in the blog, but here it was mentioned – Microsoft added the following bug in the Known Issues section for Updates for Windows 7, Windows 8.1 and Windows 10:

After installing this update, Internet Explorer may fail to load images with a backslash (\) in their relative source path.

Workaround:

Change the backslash (\) to a forward slash (/) in the relative path of the image element.

Or

Change the relative path to the full URI path.

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

Of course, it a problem, when someone in a corporate environment is dependent on Internet Explorer 11.

A fix is ready

Woody Leonhard now points out in this article that Microsoft has now provided a fix for this bug for Windows 7 SP1 and Windows 8.1. On February 19, 2019, Microsoft released the Cumulative update for Internet Explorer: February 19, 2019 KB4491113, which is intended to fix the problem.

This cumulative update includes improvements and fixes for Internet Explorer 11 that is running on Windows 8.1 or Windows 7, and resolves the following issue:

Internet Explorer cannot load images that have a backslash (\) in their relative sources path.

If someone is affected, they can install the IE update KB4491113. The update is available for download and manual installation via Microsoft Update Catalog. If you have installed language packs, you must reinstall them after applying the update. No restart is required after the update installation. 

Similar articles:
Microsoft Office Patchday (February 5, 2019)
Flash Player 32.0.0.142 released
Microsoft Security Update Summary (February 12, 2019)
Patchday: Updates for Windows 7/8.1/Server 12. Feb. 2019
Patchday Windows 10 Updates (February 12, 2019)
Patchday Microsoft Office Updates ( February 12, 2019)
Microsoft Patchday: Other Updates February 12, 2019

↧
Remove ADS
Viewing all 4454 articles
Browse latest View live

Search

  • RSSing>>
  • Latest
  • Popular
  • Top Rated
  • Trending
© 2025 //www.rssing.com
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>