📎 AI Summary:
The forum thread discusses an issue with using `netsh trace` on Windows 10 builds. The original poster, Vivi, notes that in build 630, setting `persist=yes` allowed continuous, non-overwritten network logging across reboots, but after updating to build 685, logs are overwritten upon restart. A suggested solution involves adding `overwrite=no`, but Vivi explains that this prevents circular logging and risks filling the maximum file size, which is unsuitable for their testing needs. Overall, the discussion highlights differences in `netsh trace` behavior across Windows versions and the challenge of maintaining persistent logs without overwriting or file size issues.
vivi

vivi

Senior Member
Joined
Sep 6, 2016
Messages
4
Thread Author #1
Hi All Experts,

I met the issue when I tried to use the netsh trace on Windows 10 build 685.
In previous version 630, I use the netsh trace with persist=yes to record the network message and all as normal whatever I restart the OS.

But after I update my Windows 10 to build 685, every time restart the OS will cause the netsh trace log be overwrote as latest message.
That means I lost the message before restart the OS.

Of course the command are the same between 630 and 685.
But the results are totally different.
Following are the command which I used.

netsh trace start wireless_dbg persist=yes maxSize=3000 capture=yes correlation=no tracefile=C:\wireless_dbg.etl

Best Regards,
Vivi Ma
 

Sort by date Sort by votes
Neemobeer

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
#2
Pretty sure you need to include overwrite=no otherwise when a new trace starts (IE on reboot) the file is overridden
 

Upvote 1 Downvote
Solution
vivi

vivi

Senior Member
Joined
Sep 6, 2016
Messages
4
Thread Author #3
Neemobeer said:
Pretty sure you need to include overwrite=no otherwise when a new trace starts (IE on reboot) the file is overridden
Click to expand...
Thanks for your kindly response, but I need circular to record the net logs during several test and may include several reboots. And I will stop to trace the net log when I receive the issue. If overwrite=no, the size will easily full as maxSize (3GB).

That's why I just using persist=yes on build 630 and can record several days and got the record which include older and latest message.
 

Upvote 0 Downvote
You must log in or register to reply here.