Jump to content

Windows 10 v1809 released

Arthur

By Arthur
in Windows 10

 Share

Recommended Posts

psydii

psydii

Posted
Posted

Again, other than playing around with it, there is no point in rushing to for the ISO until 3 months after the initial release. Consider it SP2 and we never deployed an OS before that did we?

 

  • 2000 (SP2)
  • XP (SP2)
  • Vista (SP2)
  • 7 (many things we relied upon weren't fixed until Enterprise Hotfix RollUp - which was sp2 by another name)
  • 8 - well, did anybody use this?
  • 8.1 - montyhly updates model appears.
  • 10 - 1511/1603 often had show stopping (for enterprise) issues until several (3) months of cumulative updates.

 

 

Let's not be in a hurry to complain - if we have time we can play and send telemetry and file bug reports, but until the three months have past it isn't ready for enterprise deployment.

  • Thanks 1
supportman

supportman

Posted
Posted
Again, other than playing around with it, there is no point in rushing to for the ISO until 3 months after the initial release. Consider it SP2 and we never deployed an OS before that did we?

 

  • 2000 (SP2)
  • XP (SP2)
  • Vista (SP2)
  • 7 (many things we relied upon weren't fixed until Enterprise Hotfix RollUp - which was sp2 by another name)
  • 8 - well, did anybody use this?
  • 8.1 - montyhly updates model appears.
  • 10 - 1511/1603 often had show stopping (for enterprise) issues until several (3) months of cumulative updates.

 

 

Let's not be in a hurry to complain - if we have time we can play and send telemetry and file bug reports, but until the three months have past it isn't ready for enterprise deployment.

Absolutely this!

Duke5A

Duke5A

Posted
Posted
Let's not be in a hurry to complain - if we have time we can play and send telemetry and file bug reports, but until the three months have past it isn't ready for enterprise deployment.

 

Heh, no way this makes it to my users any time soon. We're absolutely dead over here as far as projects and work orders are concerned. I'm bored! ;)

Arthur

Arthur

Posted
  • Author
Posted
I wonder how long before they actually release the ISO though as apparently the update was fixed last week...

Microsoft is still fixing bugs (including the annoying Task Manager bug)...

 

Windows 10 October 2018 Update Build 17763.104 Released to Insiders With Fixes

 

Windows 10 October 2018 Update Build 17763.104 is now rolling out to the Insiders in the Slow and Release Preview Ring with important fixes. This build fixes issues with the Task Manager, third-party Antivirus products, and addresses driver compatibility issues experienced by some users.

 

The update has finally fixed a bug in Task Manager that causes incorrect reporting of CPU usage. It's one of the known issues that Insiders reported during the testing of October 2018 Update, but for some reason it wasn’t fixed before the public launch.

 

In a blog post, Microsoft confirmed that Windows 10 October 2018 Update Build 17763.104 (KB4464455) is available for Slow and Release Preview rings. It fixes the following issues:

 

  • We have fixed the issue where the incorrect details were being shown in Task Manager under the “Processes” tab.
  • We fixed an issue where in certain cases IME would not work in the first process of a Microsoft Edge user session.
  • We fixed an issue where in some cases applications would become unresponsive after resuming from Connected Standby.
  • We fixed several issues causing application compatibility problems with 3rd-party antivirus and virtualization products.
  • We fixed several issues with driver compatibility.

It's important to note that Windows 10 October 2018 Update rollout is still paused and Microsoft hasn't announced the final build yet. Microsoft paused the rollout of Windows 10 October 2018 Update after they discovered a critical bug leading to data loss on a number of systems. Microsoft has already fixed the bug but the October 2018 Update is currently being tested again as part of the Windows Insider program.

  • Thanks 1
mavhc

mavhc

Posted
Posted

Year 26 of Windows NT and they're still fixing bugs.

 

I'd love to know why seemingly random things break, I suspect because they entire system is built on sand

Norphy

Norphy

Posted
Posted
Year 26 of Windows NT and they're still fixing bugs.

 

I'd love to know why seemingly random things break, I suspect because they entire system is built on sand

 

Software has bugs. Linux has been around in one form or another for 27 years, there's bugs in that. OS X/macOS has been around since 2001, there's bugs in there too. BSD has been around since 1977. Guess what? Bugs there too.

 

When your product has literally millions of lines of code, bugs are going to happen.

mavhc

mavhc

Posted
Posted
Software has bugs. Linux has been around in one form or another for 27 years, there's bugs in that. OS X/macOS has been around since 2001, there's bugs in there too. BSD has been around since 1977. Guess what? Bugs there too.

 

When your product has literally millions of lines of code, bugs are going to happen.

 

Well, main problem is they add new code.

 

But just read the random list of things that break in each beta, it's very odd.

Arthur

Arthur

Posted
  • Author
Posted

Windows 10 version 1809 plagued by another data loss issue

 

The new bug appears to affect operations with archives. A Reddit user reported that Windows 10 version 1809 would no longer prompt the user for conflict actions, e.g. when a file exists in the destination and is about to be copied to that destination.

 

Previous versions of Windows 10 would prompt the user for an action such as replacing the original file with the new copy or skipping it. Windows 10 version 1809 does not prompt according to reports but overwrites automatically in the selected destination folder.

 

Another report, this time from a thread on Ask Woody, suggests that it may also happen that the same operation fails silently by not overwriting files at all and not prompting users about it.

 

A third report on Reddit suggests that drag and drop operations from compressed folders to others appear broken as well. The copy "appears" to happen but when the user checks the files in the destination folder, files have not been updated.

 

All three reports suggest that some zip-related behaviour is broken in the operating system. The users did not reveal if they used the built-in zip functionality or a third-party application; it seems likely that the bug affects only Windows 10's built-in zip functionality and not third-party programs such as Bandizip, WinRar, or 7-Zip.

 

Comments confirm the assumption: the issue affects only the built-in Zip functionality of Windows 10 version 1809 and not that of third-party application.

matt40k

matt40k

Posted
Posted
So, what you are saying is, destroy all humans?

It's a bit drastic, but if you want bug free code, take the keyboard away from the developers. Doesn't mean you're computer will do much however!

  • Thanks 1
matt40k

matt40k

Posted
Posted
Or just find the bugs and fix them, without adding new code, eventually you must get to bug free code

If only it was that simple. First you have this thing called hardware, this is currently evolving which means the OS has to add code to deal with the new hardware. You then have this thing called the "internet" which allows computers to talk to each other across the world, unfortunately not everyone is nice on this "internet" thing and you have these group of people called "hackers" who want to break you're bug free problem by trying to make you're program do things that it wasn't suppose to do. Now at this stage things are rather complex so we need to deal with multiple teams and each part has a stack, so things lower on the stack will require the things further up the stack to update. Now again, we're humans and we are busy, so the stack might have to deal with folks not updating their bit (shocking I know), which means we might end up needing to support multiple versions of our code which makes it harder to keep bug free.

mavhc

mavhc

Posted
Posted

the best way to remove bugs is to remove code, make things simpler.

 

As hardware is mostly software too, same rules apply, new hardware will have bugs

matt40k

matt40k

Posted
Posted

Sounds like you'll like OpenBSD.

 

Problem with you're idea is, well lets say you have a 486, you can't get 486 anymore its under powered, costs too much to make, now you can only get a dual core 64bit processor. Good luck rewriting your software for that.

matt40k

matt40k

Posted
Posted
$500 for just the board. I think schools are having a hard enough time getting £30 for a raspberry pi signed off at the moment, not sure you could justify the extra cost to avoid paying ARM the licensing fee.
mavhc

mavhc

Posted
Posted

True, but we also don't want to be running old bug free software, we want new cool stuff to engage students.

 

However if you're nasa/nuclear power station/submarine maker...

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...