-
Bug
-
Resolution: Fixed
-
21w43a, 21w44a, 1.18 Pre-release 1, 1.18 Pre-release 2, 1.18 Pre-release 3, 1.18 Pre-release 4, 1.18 Pre-release 5, 1.18 Pre-release 7, 1.18 Release Candidate 3, 1.18 Release Candidate 4, 1.18, 1.18.1 Release Candidate 1, 1.18.1, 22w03a, 1.18.2 Pre-release 1, 1.18.2, 22w11a, 22w14a, 22w15a, 22w19a, 1.19 Pre-release 1, 1.19 Pre-release 3, 1.19 Release Candidate 1, 1.19, 22w24a, 1.19.1 Release Candidate 2, 1.19.1 Release Candidate 3, 1.19.1, 1.19.2 Release Candidate 1, 1.19.2, 22w42a, 22w43a, 22w46a, 1.19.3 Pre-release 2, 1.19.3 Pre-release 3, 1.19.3 Release Candidate 1, 1.19.3 Release Candidate 2, 1.19.3 Release Candidate 3, 1.19.3, 23w04a, 23w06a, 23w07a, 1.19.4 Pre-release 1, 1.19.4 Pre-release 2, 1.19.4 Pre-release 3, 1.19.4 Pre-release 4, 1.19.4 Release Candidate 1, 1.19.4 Release Candidate 3, 1.19.4, 23w12a, 23w13a, 23w14a, 23w16a, 23w17a
-
None
-
Windows 11 Pro 22H2
-
Community Consensus
-
Debug, Performance
-
Low
The bug
Minecraft can't be correctly profiled to Windows 11 version.
My Windows 11 version is currently 22H2, OS build 22621.963, but Minecraft detected it as Windows 10 (amd64) version 10.0.
Steps to reproduce
Use F3+L in the game or long press F3+C for 10 seconds to cause a crash.
Show Windows 11 version as Windows 10 (amd64) version 10.0 in system.txt and crash reports(Operating System).
- is duplicated by
-
MC-257630 Windows 10 instead of 11 on telemerty events
- Resolved
-
MC-257631 "platform" field on telemetry states Windows 10 on Windows 11 devices
- Resolved
- relates to
-
MC-237262 Crash report and tick profiling causes "Failed to find module info for _" spam to log
- Resolved
-
MCPE-146772 Minecraft detected Windows 11 as Windows 10
- Resolved
-
MC-259978 Minecraft telemetry data detected Windows 11 as Windows 10
- Resolved