TairikuOkami

Level 28
Verified
Content Creator
MS has released August updated 2004 MVS ISO (19041.450). It is probably another step for the upcoming 20H2, since it is supposed to be just a service pack and the last one actually. Beginning the next year, MS will release only one major version per year.

EDIT: Microsoft refreshes Windows 10 Media Creation Tool with Build 19041.450
 

Attachments

  • capture_08192020_222231.jpg
    capture_08192020_222231.jpg
    72.3 KB · Views: 89
Last edited:

CyberTech

Level 32
Verified
Microsoft announced this week that it enabled TLS 1.3, the latest version of the security protocol, in the latest Windows 10 builds starting with build 20170. The company notes that TLS 1.3 is enabled by default in IIS/HTTP.SYS, and that Microsoft Edge Legacy and Internet Explorer administrators may enable it in the Internet Options under Advanced.

The new Chromium-based Microsoft Edge browser supports TLS 1.3 out of the box according to Microsoft. It does not use the Windows TLS stack
Support for TLS 1.3 will also be added to .NET versions 5.0 and newer.

The enabling of TLS 1.3 in recent Windows 10 builds is the first step in the wider adoption of the security protocol on Windows 10. The company has not revealed when it plans to enable it in stable versions of Windows 10. It seems unlikely that TLS 1.3 will be enabled in the next feature update for Windows 10, Windows 10 version 20H2. A more likely candidate is Windows 10 version 21H1, the first feature update of the coming year; this would also coincide with the disabling of TLS 1.0 and 1.1 which Microsoft announced won't happen before Spring 2021.

 

amirr

Level 7
I just have this in Reliability Monitor happened yesterday. I don't do gaming on my PC.
Source
Windows

Summary
Hardware error

Date
‎8/‎24/‎2020 7:26 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 17d
Parameter 1: 41
Parameter 2: ffff95098e852270
Parameter 3: ffff95098e117570
Parameter 4: ffffe2041810fa70
OS version: 10_0_19041
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19041.2.0.0.256.48
Locale ID: 1033


I searched and found this post, but nobody replied there to him:
 

Gandalf_The_Grey

Level 36
Verified
Trusted
Content Creator
I'm on 2004 so will try report back when the update is installed. Thanks @Gandalf_The_Grey , your a rock! :love:(y)
That would be great (y)
Hope to see this bug finally being fixed this week.
With a little help of our friends at Wilders my memory integrity issue was fixed:
Then I have no more remaining bugs in 2004 and can safely begin to upgrade the systems of my family members.
 

Gandalf_The_Grey

Level 36
Verified
Trusted
Content Creator

plat1098

Level 22
Verified
Yes, I still have ESENT id 642 warnings: went from literally dozens per day when I first installed 2004 to two of them at every machine start/restart. They seem to do no harm and if start-up time is impacted in any way, it's not noticeable really.

Speaking for myself, adios 2004. 👋 😁 When's 2009 coming down the track, October maybe? Or is it 20H2 now?
 
Top