Windows 10 Insider Preview Beta Channel Build 19042.423 (20H2) July 31 Insider

dskiller said:

any known issues?>..........

The same ones as 20H1(2004)

jimbo45 said:

Hi there
working OK as a VM -- can't see any difference between this and previous version -- presumably there are some though otherwise why release a build !! I'm sure it's not just to generate "pseudo work" for bored developers !!!.

C'mon Ms --you promised a full linux kernel in the WSL2 with facility for GUI type desktop in the WSL -- I know this is still an ongoing project but what about releasing even a "pre-alpha build" --if it doesn't work ideally -- that's OK --after all this is the purpose of these testing programs surely .

On some of the other threads there's endless drivel about icons and how the menu has or hasn't changed -- seriously guys that's a trivial bit that could be fixed with more user customiseable bits in the GUI -- why not start going there too -- after all the basic Windows GUI hasn't really changed much over the years in spite of the fact that hardware today is almost "on another galaxy" compared to what was available when these editions of Windows were released.

Windows 1.01



Windows 3.11 (probably the very first "sensible useable" also as a networkable office type Windows) -- I remember it as Windows for Workgroups on a DOS LAN !!! - I think it was Novell who did the networking. It worked for sharing files (word for windows and excel - plus email but was prone to glltches -nothing new there with current Windows networking !!! so that hasn't changed much in 30 odd years.




Cheers
jimbo

Didn't have pre-emptive multi tasking so a rogue program could lock it up completely.

jimbo45 said:

Hi there
By definition surely a rogue program could hose up just about anything --

however isn't any sensible matured OS (assuming you include Windows in a sensible OS) built in such a manner that it can protect itself against badly written applications -- specialized attacks created deliberately for hacking / other malfeasant purposes excluded -- decent A/V protection helps there - and these days WD is pretty good at that.

Cheers
jimbo

In a pre-emptive multi tasking environment a program doesn't have to voluntarily give control back to the OS as was needed in pre NT windows versions. I worked for years on IBM CICS which is also a cooperative multi tasking environment and it was a big programming problem.

jimbo45 said:

Hi there
wasnt CICS that thing that if you added a new application or even a new user you had to re-start the entire subsystem !!! -- a bit like Vodafone or whoever having to shut its entire network and restart it to add a new subscriber !!!

Thank goodness days of that type of software are well and truly gone --I remember IBM's IMS DB system --hideous hierarchiacial DB system -- you could wreck the whole system by a simple application program just reading the main DB sequentially BACKWARDS !!!! --thank goodness for MySQL, MariaDB etc / other decent OO technologies and realtional DB's !!!

In the old days IBM mainframe sysprogs used to hate me -- I could wreck their systems faster than they could repair them !!!.

Cheers
jimbo

Yes you needed to restart CICS for almost any change. I also worked on IMS DB. The real killer was inserting keyed segments in key sequence. It had to read the entire chain to add it to the end. I had a DB conversion that had to be abandoned after two days, a change to a sort order and it completed in a couple of hours.

KB4568831 (Build 19041.423) released as optional update to Windows Update. Also available as Build 19042.423 to Beta Channel from WU.

KB4568831 Cumulative Update Windows 10 v2004 build 19041.423 - July 31

https://support.microsoft.com/en-us/...date-kb4568831

Installed OK!
But I still have this issue: