Jump to content

Windows 10 v1809 released

Arthur

By Arthur
in Windows 10

 Share

Recommended Posts

MartinT

MartinT

Posted
Posted

You don't install RSAT any more. You go to Settings | Apps | Manage optional features.

 

Strangely, Group Policy doesn't seem to have been included.

Jaan

Jaan

Posted
Posted
You don't install RSAT any more. You go to Settings | Apps | Manage optional features.

 

Strangely, Group Policy doesn't seem to have been included.

 

Sorry yes i should have been clearer. I installed from add new features and also managed to install GPedit from the same location.

 

Annotation.png

DJ-1701

DJ-1701

Posted
Posted
Sorry yes i should have been clearer. I installed from add new features and also managed to install GPedit from the same location.

 

[ATTACH=CONFIG]50459[/ATTACH]

 

Strangely when I select to install them, they try and disappear. Looking under the optional feature history it failed... and I should contact my administrator to get that feature...

Jaan

Jaan

Posted
Posted
Strangely when I select to install them, they try and disappear. Looking under the optional feature history it failed... and I should contact my administrator to get that feature...

 

What did he/she say?

 

 

 

 

 

 

 

 

 

 

 

 

 

Joking, this happened to me. Make sure you're online and have access to windows updates. This happened to me also.

Arthur

Arthur

Posted
  • Author
Posted

New feature or bug?

 

Windows 10 1809 - breaking change in cmd.exe "start" command behaviour

 

I originally thought this was a PowerShell issue, but it isn't. But it has a good chance of breaking certain batch files and PowerShell scripts.

 

In 1809, the way the start command (from cmd.exe) behaves has changed. You can work around it by adding /max or /min after start. Running something off a network share from a command prompt like:

 

start z:\myapp.exe

 

will now throw up a security warning dialog, when it did not in 1803 and earlier.

 

Further, a PowerShell script like this:

 

$script = { & cmd.exe /c start notepad.exe }
$job = start-job -scriptblock $script

 

would give you a job with state Running in 1803, until you closed notepad. In 1809, the job state is Completed before notepad is closed.

 

Adding /max or /min restores old behaviour for both of these.

Arthur

Arthur

Posted
  • Author
Posted

Intel have released a new graphics driver to fix this issue.

 

www.techpowerup.com/248216/intel-releases-graphics-driver-25-20-100-6323-for-windows-10

 

Intel processors running with Gen 9.5 iGPUs enabled (that's 6th generation "Skylake" or later), expose an integrated audio controller to the operating system. This controller is responsible for digital audio output through the iGPU's HDMI and DisplayPort connectors, and is similar to the one NVIDIA and AMD integrate with their discrete GPUs. Users with driver version 10.25.0.3 or older for this controller, could run into problems when Windows Update is re-loading the drivers as part of the upgrade process. Intel has since released driver version 10.25.0.10 part of the latest Graphics Drivers 25.20.100.6323. If you're still on Windows 10 version 1803 and use your iGPU, it's recommended that you update your Intel graphics drivers before initiating Windows Update to version 1809.

 

Highlights

  • Windows 10 October 2018 Update Launch Driver
  • HDR for embedded laptop panels Launch Driver

New Features

  • Enables full quality HDR10 in embedded laptop displays
  • HDR and EDR enhancements for external and laptop displays
  • Support for Wide Colour Gamut Displays
  • WinML performance optimizations
  • Support for DirectX 12 Shader Model 6.3 Compiler
  • Improves hot plug audio synchronization between the Graphics and Audio drivers
  • Performance improvements and optimizations for Pro Evolution Soccer 2019 on 6th Generation Intel Core processors or higher
  • Memory Optimizations in Vulkan
  • Improved colour quality during video playback and battery lifetime when display is in standby
  • Security fixes and improvements

Key Issues Fixed

  • Minor Graphics anomalies may be observed in Phantasy Star Online 2
  • Intermittent crashes or hangs may occur in Wolfenstein II: The New Colossus (Vulkan), Adobe Premiere Pro CC 2019 (OpenCL)
  • Checkmark indicating 'optimization' not updating correctly in the Intel Control Panel Gaming page
  • Panel Self Refresh remains disabled after full-screen video playback, which may impact battery life
  • Intermittent display flickering when display is idle on certain multi-refresh rate panels
  • Miracast display may not go full-screen in some systems
  • A Virtual Machine session may go blank when running some 3D benchmarks and YouTube* sessions, or if Graphics acceleration enabled, if using a Windows 10 October 2018 Update (RS5) driver

Arthur

Arthur

Posted
  • Author
Posted

:(

 

Microsoft Has A Software Quality Problem

 

Microsoft mainly relies on the Windows Insider program for fixing bugs on the Windows software. As Microsoft develops new updates like the October 2018 Update, it rolls out new features over weeks and months, which is then tested by Insiders. Most of the widespread problems with these new features and updates are usually noticed by Windows Insiders and later fixed by Microsoft before a major update is released to the public.

 

And then there are issues that only affect some users, leaving them buried under all the other feedback and bug reports within Feedback Hub, the app used by Windows 10 users and Insiders to report bugs and suggestions to Redmond. That’s exactly what happened with the data deletion issue. Some Windows Insiders have reported this issue as early as 3 months ago, as noted by Rafael Rivera on Twitter. If you simply open up Feedback Hub and search for “documents deleted” you will see multiple reports from Insiders where their files were automatically deleted after they installed the update.

 

Because these issues aren’t widespread, most of these reports from Insiders had low levels of upvotes, ranging from 3-10. That means Microsoft likely never even noticed these reports from Insiders, which is why is the only thing that can explain how such a major issue made it to the public release — all of that simply because of how the Insider program’s bug reporting system actually works.

 

Important issues like these are often buried under thousands of other general feedback like “Make File Explorer look more modern” or “Add Acrylic to File Explorer”. Although these are valid feedback, they often prevent actual issues from being noticed by Microsoft, and that is a fundamental problem with the entire Insider program system. Things get even worse considering the fact that Microsoft has cut down on independent testing a few years ago, relying mostly on Insiders for testing its software.

 

Microsoft’s Windows Insider team will probably find a way to explain itself here, but it’s more than apparent: the Feedback Hub simply isn’t capable of dealing with issues from millions of users, especially when the app is mostly used by fans to provide feedback — mainly fueled by their love for the OS. Critical issues are not only buried under borderline-fictional things like users asking for Acrylic on File Explorer, but they are also often buried so deep down that Microsoft’s systems never even pick them up, leading to disasters like this.

 

https://twitter.com/WithinRafael/status/1048473218917363713

 

bZiArN.png

 

MLAboY.jpg

sigma

sigma

Posted
Posted
Biggest bug in MS history? In terms of data loss

 

Microsoft have a long history of bricking users machines after updates. Some might argue that it leavers some users in a worse position.

 

This time there "might" be some official assistance:

https://www.bleepingcomputer.com/news/microsoft/microsoft-says-they-can-recover-files-deleted-by-windows-10-october-2018-update/

 

I am not being lazy by not even starting to test updates until they have been out for at least a week - except for very exceptional circumstances.

Arthur

Arthur

Posted
  • Author
Posted

First cumulative update for v1809.

 

https://support.microsoft.com/en-us/help/4464330

 

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

 

  • Addresses an issue affecting group policy expiration where an incorrect timing calculation may prematurely remove profiles on devices subject to the "Delete user profiles older than a specified number of day.”
     
     
  • Security updates to Windows Kernel, Microsoft Graphics Component, Microsoft Scripting Engine, Internet Explorer, Windows Storage and Filesystems, Windows Linux, Windows Wireless Networking, Windows MSXML, the Microsoft JET Database Engine, Windows Peripherals, Microsoft Edge, Windows Media Player, and Internet Explorer.

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

  • Thanks 1
ADMaster

ADMaster

Posted
Posted
According to Neowin that is a completely separate bug so it's still not a good idea to deploy v1809. :(

 

www.neowin.net/news/microsoft-releases-windows-10-builds-1776355-17134345---heres-whats-new

 

It doesn't address the issue that caused files to be deleted upon upgrading.

 

 

So it sounds like the bug is fixed now, but I'm still going to wait.

Update: An earlier version of this article said that the cumulative update doesn’t address the deleted files.
  • Thanks 1
Arthur

Arthur

Posted
  • Author
Posted (edited)
So it sounds like the bug is fixed now

You're right. According to Microsoft the data loss bug was caused by Known Folder Redirection. I had a feeling it might be.

 

Updated version of Windows 10 October 2018 Update released to Windows Insiders

 

Last week we paused the rollout of the Windows 10 October 2018 Update (version 1809) for all users as we investigated isolated reports of users missing files after updating. Given the serious nature of any data loss, we took the added precaution of pulling all 1809 media across all channels, including Windows Server 2019 and IoT equivalents. We intentionally start each feature update rollout slowly, closely monitoring feedback before offering the update more broadly. In this case the update was only available to those who manually clicked on “check for updates” in Windows settings. At just two days into the rollout when we paused, the number of customers taking the October 2018 Update was limited. While the reports of actual data loss are few (one one-hundredth of one percent of version 1809 installs), any data loss is serious.

 

We have fully investigated all reports of data loss, identified and fixed all known issues in the update, and conducted internal validation. Also, Microsoft Support and our retail stores customer service personnel are available at no charge to help customers. More details are available below.

 

Today we take the next step towards the re-release of the Windows 10 October 2018 Update by providing the updated version to our Windows Insider community. We will carefully study the results, feedback, and diagnostic data from our Insiders before taking additional steps towards re-releasing more broadly.

 

More Information

Prior to re-releasing the October 2018 Update our engineering investigation determined that a very small number of users lost files during the October 2018 Update. This occurred if Known Folder Redirection (KFR) had been previously enabled, but files remain in the original “old” folder location vs being moved to the new, redirected location. KFR is the process of redirecting the known folders of Windows including Desktop, Documents, Pictures, Screenshots, Videos, Camera Roll, etc. from the default folder location, c:\users\username\, to a new folder location. In previous feedback from the Windows 10 April 2018 Update, users with KFR reported an extra, empty copy of Known Folders on their device. Based on feedback from users, we introduced code in the October 2018 Update to remove these empty, duplicate known folders. That change, combined with another change to the update construction sequence, resulted in the deletion of the original “old” folder locations and their content, leaving only the new “active” folder intact. Accordingly, below are the issues we have identified and fixed:

 

  • Using KFR the user redirected a known folder to a different drive. For example, suppose you ran out of space on your C drive. You want to save some files separate from your primary folder, so you add another drive to your system for these. You create “D:\documents” and change the location of the files known folder from the original “old” location c:\users\username\documents to D:\documents. In some cases, if the contents of c:\users\username\documents were not moved to D:\documents, then a user could also encounter this issue. When the October 2018 Update was installed the original “old” folder was deleted including the files in that folder (in this example c:\users\username\documents would be deleted; d:\documents, the new location, would be preserved).
     
     
  • The user configured one or more of their Known Folders (Desktop, Documents, Pictures, Screenshots, Videos, Camera Roll, etc.) to be redirected (KFR) to another folder on OneDrive. For example, the user changed the location property of the documents folder from c:\users\username\documents to another folder. During this process the system prompts the user and asks if they would like to move the files to the new location. If the files were not moved and the October 2018 Update is installed the original “old” folder was deleted including the files in that folder.
     
     
  • The user used an early version of the OneDrive client and used the OneDrive settings to turn on the Auto save feature. This feature turned on KFR for the Documents and/or Pictures folders based on the user’s choice but did not move the existing files from the original “old” location to the new location. For example, if a user turned on Auto Save for pictures the location of the Pictures folder would be changed from c:\users\username\pictures to c:\users\username\onedrive\pictures, but no files would be moved. The current version of this feature moves the files. If the files were not moved and the October 2018 Update was installed the original “old” folder was deleted including the files in that folder (in this example c:\users\username\pictures would be deleted; c:\users\username\onedrive\pictures, the new location, would be preserved).

We have fully investigated these issues and developed solutions that resolve all three of these scenarios, so the “original” old folder location and its contents remain intact.

 

Today, we also released some other fixes in the monthly update for customers who have already taken the Windows 10 October 2018 Update. More details are available in KB 4464330.

 

https://www.zdnet.com/article/windows-10-october-2018-update-microsoft-releases-fix-for-data-deletion-bug

 

If Microsoft's estimation of the percentage of affected users is accurate, it's likely that a few hundred people were affected by this bug. The company says it will offer data recovery options but cannot guarantee the outcome of any such recovery efforts.
Edited by Arthur

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...