[1809, ou] Windows 10 v1809 released

[matt40k]

What? Nuclear power stations don't use the "on error resume next" statement all over the place

[newpersn]

Back to Topic.

 

Any one know when they are re-releasing this?

[mavhc]

Corrupt zip files now, so...never?

 

I have a theory that they changed notepad.exe, and it broke everything else, because no one's changed it in the past 20 years and it turns out everything depends on it

[Arthur]

Corrupt zip files now, so...never?

Perhaps it's worth waiting for Windows 10 v2003 (a.k.a. 19H1)?

 

I have a theory that they changed notepad.exe, and it broke everything else, because no one's changed it in the past 20 years and it turns out everything depends on it

Could it be due to this...

 

https://arstechnica.com/gadgets/2018/10/microsofts-problem-isnt-shipping-windows-updates-its-developing-them

 

A reasonable expectation is that Microsoft would have a set of tests around this new code to verify that it works correctly: create a file, check it syncs properly, delete the local copy leaving a placeholder, open the file to have the real file retrieved, delete the file entirely, and so on and so forth. There's a handful of basic operations around manipulating files and directories, and in any kind of respectable agile development process, there will be tests to verify all the operations work as expected, and make sure that the API does what it's supposed to do.

 

Moreover, one would expect any code change that broke those tests to be rejected and not integrated. The code should be fixed, and it should pass its tests, before it's ever merged into the main Windows code—much less shipped to beta testers.

 

And yet, this is not what happened: many of the preview builds had a bug wherein deleting a directory that was synced to OneDrive crashed the machine. Not only was this bug integrated into the Windows code, it was allowed to ship to end users.

 

Test the software before you ship it, not after

This tells us some fundamental things about how Windows is being developed. Either tests do not exist at all for this code (and I've been told that yes, it's permitted to integrate code without tests, though I would hope this isn't the norm), or test failures are being regarded as acceptable, non-blocking issues, and developers are being allowed to integrate code that they know doesn't work properly. From outside we can't tell exactly which situation is in play—it could even be a mix of both—but neither is good.

 

For older parts of Windows that may be a little more excusable—they were developed in an era before the value of automated testing was really recognized, and they may very well not have any real test infrastructure. But the OneDrive placeholders aren't an old part of Windows; they're leveraging a brand new set of capabilities. We might excuse old code being under-tested, but there's no good reason at all that new code shouldn't have a solid set of tests to verify basic functionality. And known defective code certainly shouldn't be merged until it's fixed, let alone shipped to testers.

 

As a result, the development of Windows 10 is still following a trajectory similar to the one it did before Windows 10. Features get merged and stability and reliability drop. The testing and stabilization phase is expected to shore things up and beat the codebase back into an acceptable shape.

 

The inadequate automated testing and/or the disregard for test failures means in turn that the Windows developers can't be confident that modifications and fixes do not have ripple effects. This is what gives rise to the "ask" phase of development: the number of changes that are accepted as the update is finalized has to be very low, because Microsoft doesn't have confidence that the scope and impact of each change is isolated. That confidence only comes with massive, disciplined testing infrastructure: you know that a change is safe because all your tests run successfully. Whatever testing the company has in place for Windows, it isn't enough to earn this confidence.

 

But in other regards, Microsoft acts as if it does have this confidence. The company does have plenty of tests; I've been told that a full test cycle for Windows takes many weeks. That full test cycle does get used—just not on the builds that actually ship. The October 2018 update is a case in point: the code was built on 15 September. It went public on 2 October. Whatever build of RS5 underwent the full testing cycle, it's not the one that we're actually using, because the full testing cycle takes too long.

 

This is a contradictory posture. It might be OK to run the full test cycle on a slightly old build if subsequent code changes were made with high confidence that they didn't break anything. But if Microsoft had high confidence that those changes wouldn't break anything, it wouldn't have to throttle them so severely in the "ask" phase.

[Arthur]

Any one know when they are re-releasing this?

13th November? That's when the .zip bug should be fixed.

 

Microsoft Confirms Windows 10 Version 1809 File Overwrite Bug

 

Microsoft has recently acknowledged a bug in Windows 10 version 1809 (October 2018 Update) that removes the file overwrite warning when extracting files from a ZIP archive to a location where data with the same name already exists.

 

However, the software giant says, even if it looks like files are being overwritten, this does not happen, and no data should be lost.

 

"With the Windows 10 October 2018 Update, if you copy or move files from a .ZIP file (without first "extracting" the contents) in to a new destination folder that contains duplicate filenames or is write-protected, you don’t get a "Do you want to replace these files” prompt", the company says.

 

"It will appear that the files were overwritten, when in fact the copy action for those files is not executed and files have not been overwritten".

 

Patch coming next month

There are three different scenarios when the process could fail, and at least one of them could cause data to be overwritten, the company explains. The bug can occur when copying files from a ZIP file to a regular folder, moving items from a ZIP to a regular folder, or copying files from a ZIP to a protected folder.

 

"While the copy action for the duplication file names does not complete and no files are overwritten, the "move" command will also silently fail and might remove/delete the moved file", the software giant notes.

 

Microsoft goes on to recommend users to extract files from ZIP archives to new locations to avoid the bug, and says that a fix is already on the way and it should be released in a future update. The patch will be released in early November, it says, so Microsoft may be waiting for next month’s Patch Tuesday to ship a fix. The November 2018 Patch Tuesday rollout is projected to kick off on the 13th.

[Zoom7000]

I wonder when they will finally take the plunge and release another ISO

[Arthur]

Yet another bug!

 

https://www.ghacks.net/2018/10/24/add-font-display-issues-to-the-growing-number-of-windows-10-version-1809-issues

 

Reports are coming in (via Windows Latest) that users who upgraded their devices running Windows 10 to the October 2018 Update -- Windows 10 version 1809 -- may face yet another issue.

 

The issue at hand this time is display related. Machines affected by the issue display garbled or entirely unreadable text.

 

The screenshot below shows how the Settings application may look like on a system that is affected by the bug.

 

Errors seem to have appeared first in the Foobar 2000 application but it did not take long before users reported that fonts were broken in web browsers such as Chrome or internal system applications such as the Settings application.

 

The most likely explanation for the garbled font issue is that it is a font fallback issue. Windows uses font fallback options when it cannot display a certain glyph because of the font that is used.

 

Basically, when Windows can't use the default font to display a glyph on the screen it uses a fallback instead.

 

The issue appeared in Windows 10 version 1809, the new feature update, on affected machines and did not exist in previous versions of Windows.

 

Some users reported that they fixed the issue by installing the latest graphics drivers on the machine. Intel users may head over to the Intel website to download the latest drivers for the integrated graphics adapter. AMD and Nvidia drivers are available as well.

 

It appears that the installation of the latest video card driver updates the font usage of the Windows 10 operating system as well; at least that is what is reported by users who fixed affected machines by updating video card drivers on the PCs.

 

 

I have experienced this bug myself. I thought my monitor or graphics card was starting to fail.

[free780]

I've actually had the SCCM console get strange black bars and freeze. But I put it down to 3rd party addins and display driver. I get the occasional pausing but could be several 3rd party applications.

[Norphy]

Oy vey.

 

I think Microsoft need a Snow Leopard edition of W10. Don’t put new features in, just make sure what they’ve got there already works and is optimised. This is getting silly.

[free780]

1903 - The stability update.

[Arthur]

Group Policy Settings Reference Spreadsheet for Windows 10 v1809 and Windows Server 2019

[Zoom7000]

I've started to fear for 1809 when you post on this thread Arthur! lol! [emoji23]

[Roberto]

Oy vey.

 

I think Microsoft need a Snow Leopard edition of W10. Don’t put new features in, just make sure what they’ve got there already works and is optimised. This is getting silly.

 

Agreed. If Microsoft want to move fast on releases, why not a "Tick/Tock" approach - "New features" release then "Stability release" each year.

[DJ-1701]

Agreed. If Microsoft want to move fast on releases, why not a "Tick/Tock" approach - "New features" release then "Stability release" each year.

 

So then we only update the once a year?

[gshaw]

Agreed. If Microsoft want to move fast on releases, why not a "Tick/Tock" approach - "New features" release then "Stability release" each year.

 

I think they'd have a much more stable product if they just released it once a year, with the 6-monthly "new features" Insider Beta. They've got something close to that with the various Slow \ Fast rings but having two finalised releases seems to end up with neither being particularly stable.

 

It'll be interesting to see how MS manage this going forward with the extended support lifecycle, seems to leave quite a large possibility of fragmentation as organisations standardise on one particular build for as long as possible. In my case it's 1709 and until there's something worthwhile in a newer build that makes as big a difference as, say Files on Demand (or Exploit Guard on the security front) I'll stick with it.

[Norphy]

The thing that's annoying me at the moment is this: I'm running 1709 here. 1709 will be supported for 30 months from release but that means that it'll only be supported until April 2020. It still means that something will have to be rolled out in Summer 2019, whether it's a brand new image or an in-place upgrade. Unless you want to do an OS upgrade in the middle of the academic year anyway

 

It's frustrating really. We can all see what a disaster 1809 has been but 1909 isn't going to be ready for Summer 2019 so that leaves us with three choices that, really, all suck:

 

1) Deploy 1809, a release that's had a bad start in life but will have another 18 months of support from Summer 2019. However, the build will still expire in April 2021 so we won't be able to get two years out of that build so realistically, we will have to update again in Summer 2020 using 1909 or 2003.

2) Deploy 1903, a release which will have a 18 month support period and will expire in October 2020 so will have to be updated in Summer 2020, whether I like it or not.

3) Deploy 1809 or 1903 during the summer then update it again when 1909 comes along. And as we've seen, using bleeding edge Windows 10 is rarely a good idea.

 

LTSC isn't a consideration for me, I don't want to be limited to not allowing WPF apps or to an old version of Office. Admittedly there are no WPF apps that people want to use right now but there might be later on and I don't want to be caught with my trousers down.

[mavhc]

Just in place upgrade, it's fine.

 

Versions of Win10 fragmentation is still less fragmentation than having 50% of people on the one you released 9 years ago, and have had 3 OS releases since

[gshaw]

LTSC isn't a consideration for me, I don't want to be limited to not allowing WPF apps or to an old version of Office. Admittedly there are no WPF apps that people want to use right now but there might be later on and I don't want to be caught with my trousers down.

Microsoft Whiteboard looks good, shame MS made the Store such a pain to work with we'd need to move our system management platform to SCCM to deploy it neatly

[DJ-1701]

UPDATE 10/30: We have released the Windows 10 October 2018 Update Build 17763.107 (KB4464455) to Windows Insiders in the Slow and Release Preview rings.

 

This Cumulative Update contains the same fixes as Build 17763.104 plus these two additional fixes:

• We fixed the issue where dragging (extracting) files from a .zip file in File Explorer to a write-protected location you don’t get a “Do you want to replace these files” prompt and the copy action fails silently.
  
• We fixed an issue causing roaming profiles to not work correctly.
  

 

Source: https://blogs.windows.com/windowsexperience/2018/09/18/announcing-windows-10-insider-preview-build-17763/#fD6OAQy0o2z4R40A.97

[gshaw]

Microsoft Whiteboard looks good, shame MS made the Store such a pain to work with we'd need to move our system management platform to SCCM to deploy it neatly

 

Quoting my past self as a correction - turns out it's possibly to deploy UWP apps with DISM, which can be used via any deployment method

[sted]

Quoting my past self as a correction - turns out it's possibly to deploy UWP apps with DISM, which can be used via any deployment method

 

but only iirc if you can get the files to download which isnt often iirc ive got it working for minecraft because there is/was a download button on the store for business bu thats about it

[Zoom7000]

Is there any news on a re-release date for the 1809 ISO?

[CHiLL]

Is there any news on a re-release date for the 1809 ISO?

Last I heard was that Microsoft released hotfixes for 1809 to the slow-ring for the various issues. I don't think they've announced anything since that.

[Arthur]

Is there any news on a re-release date for the 1809 ISO?

November?

 

(This year )

[free780]

Well.

I think patch Tuesday will be the release date.