Microsoft
Task Scheduler
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2019-1069 | 12 Jun 2019 | Windows 10 Version 1703: 10.0.0 < publication; Windows 10 Version 1803: 10.0.0 < publication; Windows Server, version 1803 (Server Core Installation): 10.0.0 < publication; Windows 10 Version 1809: 10.0.17763.0 < publication, 10.0.0 < publication; Windows Server 2019: 10.0.17763.0 < publication; Windows Server 2019 (Server Core installation): 10.0.17763.0 < publication; Windows 10 Version 1709 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1709: 10.0.0 < publication; Windows 10 Version 1903 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1903 for x64-based Systems: 10.0.0 < publication; Windows 10 Version 1903 for ARM64-based Systems: 10.0.0 < publication; Windows Server, version 1903 (Server Core installation): 10.0.0 < publication; Windows 10 Version 1507: 10.0.10240.0 < publication; Windows 10 Version 1607: 10.0.14393.0 < publication; Windows Server 2016: 10.0.14393.0 < publication; Windows Server 2016 (Server Core installation): 10.0.14393.0 < publication | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.