From 1e67889b32d20059a4b1809ad3da993255754003 Mon Sep 17 00:00:00 2001
From: Jason E <31452365+jasonepperly@users.noreply.github.com>
Date: Fri, 8 May 2026 07:57:42 -0400
Subject: [PATCH] Update provider registration limits in documentation

Clarified provider registration limits for Windows versions.
---
 .../content/evntprov/nf-evntprov-eventregister.md    | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/sdk-api-src/content/evntprov/nf-evntprov-eventregister.md b/sdk-api-src/content/evntprov/nf-evntprov-eventregister.md
index 5549aff99b7f..9ffdca4f4c9d 100644
--- a/sdk-api-src/content/evntprov/nf-evntprov-eventregister.md
+++ b/sdk-api-src/content/evntprov/nf-evntprov-eventregister.md
@@ -163,14 +163,14 @@ ignore failures returned by **EventRegister**. In case of failure,
 uses of the RegHandle (i.e. in calls to **EventWrite** and **EventUnregister**)
 will have no effect.
 
-Each process can register up to 1,024 providers. However, you should limit the
-number of providers that your component registers to one or two. This limit
-includes providers registered using this function and providers registered using
+**Prior to Windows Vista:** there was no specific limit to the number of
+providers that a process can register. Starting with **Windows 7** each process
+can register up to 1,024 providers. In **Windows 8** and later each process can
+register up to 2048 providers. However, you should limit the number of providers
+that your component registers to one or two. This limit includes providers
+registered using this function and providers registered using
 [RegisterTraceGuids](/windows/desktop/ETW/registertraceguids).
 
-**Prior to Windows Vista:** There is no specific limit to the number of
-providers that a process can register.
-
 ## -see-also
 
 [EnableCallback](/windows/desktop/api/evntprov/nc-evntprov-penablecallback)