Godlike Productions - Discussion Forum
Users Online Now: 1,464 (Who's On?)Visitors Today: 498,212
Pageviews Today: 807,766Threads Today: 229Posts Today: 4,258
08:28 AM


Rate this Thread

Absolute BS Crap Reasonable Nice Amazing
 

Why does everyone here hate Windows 10 so much?

 
Anonymous Coward (OP)
User ID: 77563213
Bulgaria
01/19/2020 12:24 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
windows 10 is complete spyware that you cant turn off, its been posted about and proven on here and all over the internet.

this is what windows 10 and with updates 7 and 8 and 8.1 ...

always listens to your microphone - sends everything it hears to microsoft, both raw audio and a speach to text translation.

cortana voice assistant sends the speach translation in text to microsoft.

microsoft keylogger installed sends every key you press to microsoft, no doubt they do the same with the mouse.

every websites you visit / internet history / passwords / forms data - everything is sent to microsoft.

wifi passwords - sent to microsoft.

always records your computer camera - all video sent to microsoft.

takes requent screenshots of your desktop screen every short amount of time, around 30 seconds or more - packages the images up and sends to microsoft.

goes through all of your files, not just names but contents - sends to micisoft.

finds out every software you have installed including whether its pirated, goes through all your removable drives - sends all info to microsoft.

all of the above has been proven fact over multiple online articles that have researched all of this.

if that wasnt enough there are backdoors into all windows pc's, most hardware components including hard drives and processors that let anyone who has the keys into your pc, mostly unseen by you.

no doubt everything in your windows 10 pc is spyed on by microsoft and sent to microsoft servers, including your ram memory, everything.

it disregards your customer experience ceip settings and spys regardless, you cannot turn off diag / telemetry / tracker the sending of all your data to microsoft and you cannot turn off windows updates that add even more spying.

microsoft even brought all this spying to windows 7 but at least you can turn off the updates. they even hid more spying updates within a security only update just to catch out 6he clever ones.
 Quoting: Anonymous Coward 74993099


collected by the nsa / cia and shared with the 5 eyes.

you have no privacy.

windows 10 users are making their job easy.
 Quoting: Anonymous Coward 74993099


Cyber criminals seem to have enough privacy.
 Quoting: Anonymous Coward 77563213


not on windows 10
 Quoting: Anonymous Coward 74993099


Most use Windows 10.
Anonymous Coward
User ID: 78298213
United States
01/19/2020 12:25 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Windows XP was the best. I still run it.
 Quoting: Anonymous Coward 62939630


The 32 bit version is good, but the 64 bit version suffered from a lack of useful native apps.
CK Dexter Haven

User ID: 77047820
Netherlands
01/19/2020 12:25 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Man if windows 10 is spying on me they must be super bored.

listening to me yell at people in online games or just keyboard clicking noises
 Quoting: Anonymous Coward 42079668


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
Anonymous Coward
User ID: 74993099
United Kingdom
01/19/2020 12:25 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
why is this even a thing?...

[link to www.safer-networking.org (secure)]
Anonymous Coward
User ID: 72447630
United States
01/19/2020 12:26 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
windows 10 is complete spyware that you cant turn off, its been posted about and proven on here and all over the internet.

this is what windows 10 and with updates 7 and 8 and 8.1 ...

always listens to your microphone - sends everything it hears to microsoft, both raw audio and a speach to text translation.

cortana voice assistant sends the speach translation in text to microsoft.

microsoft keylogger installed sends every key you press to microsoft, no doubt they do the same with the mouse.

every websites you visit / internet history / passwords / forms data - everything is sent to microsoft.

wifi passwords - sent to microsoft.

always records your computer camera - all video sent to microsoft.

takes requent screenshots of your desktop screen every short amount of time, around 30 seconds or more - packages the images up and sends to microsoft.

goes through all of your files, not just names but contents - sends to micisoft.

finds out every software you have installed including whether its pirated, goes through all your removable drives - sends all info to microsoft.

all of the above has been proven fact over multiple online articles that have researched all of this.

if that wasnt enough there are backdoors into all windows pc's, most hardware components including hard drives and processors that let anyone who has the keys into your pc, mostly unseen by you.

no doubt everything in your windows 10 pc is spyed on by microsoft and sent to microsoft servers, including your ram memory, everything.

it disregards your customer experience ceip settings and spys regardless, you cannot turn off diag / telemetry / tracker the sending of all your data to microsoft and you cannot turn off windows updates that add even more spying.

microsoft even brought all this spying to windows 7 but at least you can turn off the updates. they even hid more spying updates within a security only update just to catch out 6he clever ones.
 Quoting: Anonymous Coward 74993099


collected by the nsa / cia and shared with the 5 eyes.

you have no privacy.

windows 10 users are making their job easy.
 Quoting: Anonymous Coward 74993099


The OP sheepand his sockpuppetssheepsheepsheep are either shills or stupid.
But gamers that live in their parent's basement gotta believe in something besides bernie.

:)
CK Dexter Haven

User ID: 77047820
Netherlands
01/19/2020 12:26 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


collected by the nsa / cia and shared with the 5 eyes.

you have no privacy.

windows 10 users are making their job easy.
 Quoting: Anonymous Coward 74993099


Cyber criminals seem to have enough privacy.
 Quoting: Anonymous Coward 77563213


not on windows 10
 Quoting: Anonymous Coward 74993099


Most use Windows 10.
 Quoting: Anonymous Coward 77563213

norespect
Anonymous Coward
User ID: 78186363
Canada
01/19/2020 12:26 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Tracks your performance and makes a model of the user and what they do on the PC.

It creates hidden folders and installs programs which you as the Admin have no power to alter if you wanted too.

Major spyware program.
Anonymous Coward
User ID: 76228459
United States
01/19/2020 12:26 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


My iMac was well over 2K and has an i7,

It also boots in about 7 seconds....
 Quoting: Topper the Grey


lmao

Boot time comes from your ssd, which you can get for 25 bucks from microcenter.

My 10 year old hp laptop boots in 7 seconds.
 Quoting: Anonymous Coward 42079668


I've had two HP's they used to be the best, neither was less than 1K + so not sure what you mean by over paying for OS.

Macs are simply what HP USED TO BE, with a 10x better OS
 Quoting: Topper the Grey


you are overpaying for the hardware

i can go to microcenter right now and piece together a custom built PC for about 1500 that will run any modern game on max settings

add in a 400 dollar 240 hz monitor and mouse and keyboard you have a modern gaming setup for about 2k

you can't get that kind of performance going with apple, it's just not possible

their hardware is way overpriced and everything you get has to be "apple" to be compatible.

you are one of these poor souls that have to constantly justify the insane prices you pay
 Quoting: Anonymous Coward 42079668


Not same quality parts maybe, and certainly with no warranty right? I can make an AR, but I have the money to buy Daniel Defense because my time is money....
Anonymous Coward
User ID: 78298213
United States
01/19/2020 12:27 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


collected by the nsa / cia and shared with the 5 eyes.

you have no privacy.

windows 10 users are making their job easy.
 Quoting: Anonymous Coward 74993099


Cyber criminals seem to have enough privacy.
 Quoting: Anonymous Coward 77563213


not on windows 10
 Quoting: Anonymous Coward 74993099


Most use Windows 10.
 Quoting: Anonymous Coward 77563213


You need to disable services with a vengeance! Much of the bullshit can be contained by disabling services, but I'd not count on all of it. I only use that fucked up OS when I'm away from home on other people's computers.
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:28 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


lmao

Boot time comes from your ssd, which you can get for 25 bucks from microcenter.

My 10 year old hp laptop boots in 7 seconds.
 Quoting: Anonymous Coward 42079668


I've had two HP's they used to be the best, neither was less than 1K + so not sure what you mean by over paying for OS.

Macs are simply what HP USED TO BE, with a 10x better OS
 Quoting: Topper the Grey


you are overpaying for the hardware

i can go to microcenter right now and piece together a custom built PC for about 1500 that will run any modern game on max settings

add in a 400 dollar 240 hz monitor and mouse and keyboard you have a modern gaming setup for about 2k

you can't get that kind of performance going with apple, it's just not possible

their hardware is way overpriced and everything you get has to be "apple" to be compatible.

you are one of these poor souls that have to constantly justify the insane prices you pay
 Quoting: Anonymous Coward 42079668


Not same quality parts maybe, and certainly with no warranty right? I can make an AR, but I have the money to buy Daniel Defense because my time is money....
 Quoting: Topper the Grey


no not same quality parts, better quality

and yes everything from microcenter comes with a receipt

they are super friendly and helpful with returns and issues with products and they can even build the PC for you in house and test it before you leave

try getting that level of service in an apple store.
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:29 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


I've had two HP's they used to be the best, neither was less than 1K + so not sure what you mean by over paying for OS.

Macs are simply what HP USED TO BE, with a 10x better OS
 Quoting: Topper the Grey


you are overpaying for the hardware

i can go to microcenter right now and piece together a custom built PC for about 1500 that will run any modern game on max settings

add in a 400 dollar 240 hz monitor and mouse and keyboard you have a modern gaming setup for about 2k

you can't get that kind of performance going with apple, it's just not possible

their hardware is way overpriced and everything you get has to be "apple" to be compatible.

you are one of these poor souls that have to constantly justify the insane prices you pay
 Quoting: Anonymous Coward 42079668


Not same quality parts maybe, and certainly with no warranty right? I can make an AR, but I have the money to buy Daniel Defense because my time is money....
 Quoting: Topper the Grey


no not same quality parts, better quality

and yes everything from microcenter comes with a receipt warranty

they are super friendly and helpful with returns and issues with products and they can even build the PC for you in house and test it before you leave

try getting that level of service in an apple store.
 Quoting: Anonymous Coward 42079668
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:30 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Man if windows 10 is spying on me they must be super bored.

listening to me yell at people in online games or just keyboard clicking noises
 Quoting: Anonymous Coward 42079668


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
 Quoting: CK Dexter Haven


if you are doing something illegal online you need to be caught

if you aren't doing anything illegal you have nothing to worry about

only criminals have something to hide
Anonymous Coward (OP)
User ID: 77563213
Bulgaria
01/19/2020 12:30 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


Cyber criminals seem to have enough privacy.
 Quoting: Anonymous Coward 77563213


not on windows 10
 Quoting: Anonymous Coward 74993099


Most use Windows 10.
 Quoting: Anonymous Coward 77563213


You need to disable services with a vengeance! Much of the bullshit can be contained by disabling services, but I'd not count on all of it. I only use that fucked up OS when I'm away from home on other people's computers.
 Quoting: Anonymous Coward 78298213


What could you possibly be doing to warrant that?
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:31 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
windows 10 is complete spyware that you cant turn off, its been posted about and proven on here and all over the internet.

this is what windows 10 and with updates 7 and 8 and 8.1 ...

always listens to your microphone - sends everything it hears to microsoft, both raw audio and a speach to text translation.

cortana voice assistant sends the speach translation in text to microsoft.

microsoft keylogger installed sends every key you press to microsoft, no doubt they do the same with the mouse.

every websites you visit / internet history / passwords / forms data - everything is sent to microsoft.

wifi passwords - sent to microsoft.

always records your computer camera - all video sent to microsoft.

takes requent screenshots of your desktop screen every short amount of time, around 30 seconds or more - packages the images up and sends to microsoft.

goes through all of your files, not just names but contents - sends to micisoft.

finds out every software you have installed including whether its pirated, goes through all your removable drives - sends all info to microsoft.

all of the above has been proven fact over multiple online articles that have researched all of this.

if that wasnt enough there are backdoors into all windows pc's, most hardware components including hard drives and processors that let anyone who has the keys into your pc, mostly unseen by you.

no doubt everything in your windows 10 pc is spyed on by microsoft and sent to microsoft servers, including your ram memory, everything.

it disregards your customer experience ceip settings and spys regardless, you cannot turn off diag / telemetry / tracker the sending of all your data to microsoft and you cannot turn off windows updates that add even more spying.

microsoft even brought all this spying to windows 7 but at least you can turn off the updates. they even hid more spying updates within a security only update just to catch out 6he clever ones.
 Quoting: Anonymous Coward 74993099


collected by the nsa / cia and shared with the 5 eyes.

you have no privacy.

windows 10 users are making their job easy.
 Quoting: Anonymous Coward 74993099


The OP sheepand his sockpuppetssheepsheepsheep are either shills or stupid.
But gamers that live in their parent's basement gotta believe in something besides bernie.

:)
 Quoting: Anonymous Coward 72447630


yes lets give criminals more privacy online

what do you have to hide?

i don't have anything to hide
Anonymous Coward
User ID: 72447630
United States
01/19/2020 12:31 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Man if windows 10 is spying on me they must be super bored.

listening to me yell at people in online games or just keyboard clicking noises
 Quoting: Anonymous Coward 42079668


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
 Quoting: CK Dexter Haven


if you are doing something illegal online you need to be caught

if you aren't doing anything illegal you have nothing to worry about

only criminals have something to hide
 Quoting: Anonymous Coward 42079668

sheepsheepsheep
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:33 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
 Quoting: CK Dexter Haven


if you are doing something illegal online you need to be caught

if you aren't doing anything illegal you have nothing to worry about

only criminals have something to hide
 Quoting: Anonymous Coward 42079668

sheepsheepsheep
 Quoting: Anonymous Coward 72447630


no i'm just not a criminal looking at things i shouldn't be
Anonymous Coward
User ID: 78132959
United States
01/19/2020 12:33 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Its a bloaty piece of "spyware as a service". A real POS compared to Windows 7 or even XP for that matter.
 Quoting: Anonymous Coward 72794704


Care to expand on what you are claiming?
 Quoting: Anonymous Coward 77563213


LOL
would take too long.

take your pick

[link to www.nope?q=windows+10+sucks&rlz=1CAHKDC_enUS850&source=lnms&t​bm=isch&sa=X&ved=2ahUKEwjrpL6B9o7nAhVD_J4KHfUsAK0Q_AUoA3oECA4​QBQ&biw=1366&bih=641#imgrc=_ (secure)]
CK Dexter Haven

User ID: 77047820
Netherlands
01/19/2020 12:34 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Man if windows 10 is spying on me they must be super bored.

listening to me yell at people in online games or just keyboard clicking noises
 Quoting: Anonymous Coward 42079668


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
 Quoting: CK Dexter Haven


if you are doing something illegal online you need to be caught

if you aren't doing anything illegal you have nothing to worry about

only criminals have something to hide
 Quoting: Anonymous Coward 42079668

ura_idiot
Anonymous Coward
User ID: 53625044
United Kingdom
01/19/2020 12:34 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
I'm curious what people do with linux?

You can't game on it.

Really what's the point of a pc if you aren't gaming?
 Quoting: Anonymous Coward 42079668


You've obviously never had to do any work...
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:34 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
...


Yeah exactly. I dont know what these B00M3rs are trying to hide thats so damn important.
 Quoting: Anonymous Coward 77563213

That's your argument for abandoning control over your OS and your privacy?

1dunno1
 Quoting: CK Dexter Haven


if you are doing something illegal online you need to be caught

if you aren't doing anything illegal you have nothing to worry about

only criminals have something to hide
 Quoting: Anonymous Coward 42079668

:ura_idiot:
 Quoting: CK Dexter Haven


great retort!
Anonymous Coward
User ID: 42079668
United States
01/19/2020 12:35 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
I'm curious what people do with linux?

You can't game on it.

Really what's the point of a pc if you aren't gaming?
 Quoting: Anonymous Coward 42079668


You've obviously never had to do any work...
 Quoting: Anonymous Coward 53625044


not on a computer no

physical labor yes
CK Dexter Haven

User ID: 77047820
Netherlands
01/19/2020 12:42 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Fuck Microsoft!

In the spring of 2016 they betrayed their long time loyal customers.

Over the years they got thousands of dollars out of me.
Never again, never another penny from me on any microsoft product computer gaming or other.

Eat Shit Microsoft
Anonymous Coward
User ID: 78186363
Canada
01/19/2020 12:46 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Also has the ability to use local networks to send info either by wifi, Bluetooth or even wireless connections to any peripheral within its range without you knowing.

Phones do the same thing.. went through 6 phones, 4 different models and found it connected to the net, cloud, even when there was no sim and the wifi was turned off. They'd connect my PC to the net via other modems in the area even if I had my computer in Air Plane mode which means no wifi connections allowed.. but it still connected.

Both phone and the computer emulated that it was turned off by turning the lights off but they were still on.. had 4 months of resolving a hack I thought was from some hacker only to find out it was MS and Google that were hacking me.

For example when windows did an update for a driver it usually shows the site it received the file it downloaded from and one file liked me to a site that no longer existed.

They give the impression that a valid program/driver was installed only to be something unexpected being installed to a hidden folder you have no access too.

I only use a flip phone now.. and we came to an understanding after my 20th reinstall with MS. I was able to access those hidden folders and open files I was restricted from. They left me alone after I just went along with their protocol.

I kid you not.. they even installed an AI on my computer to counter what I was doing when I was digging.

When I went to the library to communicate my findings they even found me there and created issues with me accessing my email accounts.

This all started when I found that they changed my system and new what I was doing for 9 months. Based on files created on a certain date. Then they created a new drive for them to work off of and were emulating my desktop with a browser. When I attempted to fix the problem this is when I found out my C drive no longer existed and they had the OS take over. My restore points were no longer working and the boot drive got corrupted. I found this out through DOS.

Went to the police station with the computer and 3 phones to inform them of the hack but they refused to listen. After the 3rd time there the front desk lady informed me that she heard similar stories from others... they turned me away with my evidence.
Anonymous Coward
User ID: 78360592
Australia
01/19/2020 12:47 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Even slot machines don't use windows anymore, they are mostly all Linux based.

Windows is finished, it is outdated and far too intrusive.
Anonymous Coward
User ID: 46504284
United States
01/19/2020 12:48 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
it spies on you, it reboots and updates randomly, updates take hours even on lightning fast computers 1000000x as powerful as supercomputers from just 20 years ago, it looks ugly, buggy updates are often pushed and then retracted, i could go on

OpenBSD is the OS of the future, it's made to be secure but you have to be kind of an expert to even think about using it. Otherwise there's Debian.
 Quoting: Anonymous Coward 78301142


I have never once had a crash using it. Updates take a few minutes not hours with Ryzen 2nd gen Cpu. Maybe you PC is outdated, this could be the problem.

They likley just gather metadata not associated with you, its not spying.
 Quoting: Anonymous Coward 77563213


It sends in a screen capture every 30 seconds. This has been proven with DPI.
Anonymous Coward
User ID: 77416747
United States
01/19/2020 12:51 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Windows 10 works flawlessly as far as I can tell. Its very impressive for gaming and multimedia processing in UHD 4k.

What gives? Its so much better than Windows 7.
 Quoting: Anonymous Coward 77563213


specialstupid

tree fitty for the deep state shill
Anonymous Coward
User ID: 78186363
Canada
01/19/2020 12:56 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
windows 10 is complete spyware that you cant turn off, its been posted about and proven on here and all over the internet.

this is what windows 10 and with updates 7 and 8 and 8.1 ...

always listens to your microphone - sends everything it hears to microsoft, both raw audio and a speach to text translation.

cortana voice assistant sends the speach translation in text to microsoft.

microsoft keylogger installed sends every key you press to microsoft, no doubt they do the same with the mouse.

every websites you visit / internet history / passwords / forms data - everything is sent to microsoft.

wifi passwords - sent to microsoft.

always records your computer camera - all video sent to microsoft.

takes requent screenshots of your desktop screen every short amount of time, around 30 seconds or more - packages the images up and sends to microsoft.

goes through all of your files, not just names but contents - sends to micisoft.

finds out every software you have installed including whether its pirated, goes through all your removable drives - sends all info to microsoft.

all of the above has been proven fact over multiple online articles that have researched all of this.

if that wasnt enough there are backdoors into all windows pc's, most hardware components including hard drives and processors that let anyone who has the keys into your pc, mostly unseen by you.

no doubt everything in your windows 10 pc is spyed on by microsoft and sent to microsoft servers, including your ram memory, everything.

it disregards your customer experience ceip settings and spys regardless, you cannot turn off diag / telemetry / tracker the sending of all your data to microsoft and you cannot turn off windows updates that add even more spying.

Microsoft even brought all this spying to windows 7 but at least you can turn off the updates. they even hid more spying updates within a security only update just to catch out 6he clever ones.
 Quoting: Anonymous Coward 74993099


Proven? Not likely. Paranoid Alex Jones style delusions, definitely.
 Quoting: Anonymous Coward 77563213


What he stated is fact.

During my time, 4 months or more, I experienced all of the above.

During the process of trying to access some files I found a file that was data mining everything your computer did and kept track of ALL information it had..

They even connected to the net through other modems in the neighborhood when I had it in Air Plane mode and had my modem off. They even gave me a hard time when I wanted to connect to my own network. Won't get into specifics. I have over 30 years computer exp..
Anonymous Coward
User ID: 78076561
01/19/2020 12:59 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
Eh, it spies..That smarter than you phone does this as well.
That smart TV, fridge and can opener do to.

Get this....Those machines around you also look into what other machines are doing.
identifying every keystroke by electronic pulse via wifi.

But go ahead and worry about the window in the machine...A perfect 10.
Anonymous Coward
User ID: 78186363
Canada
01/19/2020 01:03 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
And example of a file I was able to get access too.. you be the judge if you don't think this is infringing on you...

File name PerStringBackup in Windows 10.

[Perflib]
Base Index=1847
Last Counter=7950
Last Help=7951

[PERF_.NET CLR Data]
First Counter=6966
First Help=6967
Last Counter=6978
Last Help=6979

[PERF_.NET CLR Networking]
First Counter=5840
First Help=5841
Last Counter=5850
Last Help=5851

[PERF_.NET CLR Networking 4.0.0.0]
First Counter=6752
First Help=6753
Last Counter=6778
Last Help=6779

[PERF_.NET Data Provider for Oracle]
First Counter=6088
First Help=6089
Last Counter=6116
Last Help=6117

[PERF_.NET Data Provider for SqlServer]
First Counter=6936
First Help=6937
Last Counter=6964
Last Help=6965

[PERF_.NETFramework]
First Counter=5868
First Help=5869
Last Counter=6042
Last Help=6043

[PERF_BITS]
First Counter=4598
First Help=4599
Last Counter=4614
Last Help=4615

[PERF_ESENT]
First Counter=2326
First Help=2327
Last Counter=4188
Last Help=4189

[PERF_Intel Storage Counters]
First Counter=7936
First Help=7937
Last Counter=7950
Last Help=7951

[PERF_MSDTC]
First Counter=4950
First Help=4951
Last Counter=4976
Last Help=4977

[PERF_MSDTC Bridge 3.0.0.0]
First Counter=7630
First Help=7631
Last Counter=7652
Last Help=7653

[PERF_MSDTC Bridge 4.0.0.0]
First Counter=6728
First Help=6729
Last Counter=6750
Last Help=6751

[PERF_rdyboost]
First Counter=4558
First Help=4559
Last Counter=4578
Last Help=4579

[PERF_RemoteAccess]
First Counter=4616
First Help=4617
Last Counter=4654
Last Help=4655

[PERF_ServiceModelEndpoint 3.0.0.0]
First Counter=7654
First Help=7655
Last Counter=7692
Last Help=7693

[PERF_ServiceModelOperation 3.0.0.0]
First Counter=7724
First Help=7725
Last Counter=7754
Last Help=7755

[PERF_ServiceModelService 3.0.0.0]
First Counter=7562
First Help=7563
Last Counter=7628
Last Help=7629

[PERF_SMSvcHost 3.0.0.0]
First Counter=7694
First Help=7695
Last Counter=7722
Last Help=7723

[PERF_SMSvcHost 4.0.0.0]
First Counter=6980
First Help=6981
Last Counter=7008
Last Help=7009

[PERF_TapiSrv]
First Counter=1900
First Help=1901
Last Counter=1918
Last Help=1919

[PERF_TermService]
First Counter=4202
First Help=4203
Last Counter=4202
Last Help=4203

[PERF_UGatherer]
First Counter=2020
First Help=2021
Last Counter=2124
Last Help=2125

[PERF_UGTHRSVC]
First Counter=2126
First Help=2127
Last Counter=2196
Last Help=2197

[PERF_usbhub]
First Counter=4978
First Help=4979
Last Counter=5012
Last Help=5013

[PERF_Windows Workflow Foundation 3.0.0.0]
First Counter=7518
First Help=7519
Last Counter=7560
Last Help=7561

[PERF_Windows Workflow Foundation 4.0.0.0]
First Counter=6044
First Help=6045
Last Counter=6086
Last Help=6087

[PERF_WSearchIdxPi]
First Counter=2198
First Help=2199
Last Counter=2324
Last Help=2325

[PerfStrings_001]
1=1847
2=System
3=The System performance object consists of counters that apply to more than one instance of a component processors on the computer.
4=Memory
5=The Memory performance object consists of counters that describe the behavior of physical and virtual memory on the computer. Physical memory is the amount of random access memory on the computer. Virtual memory consists of the space in physical memory and on disk. Many of the memory counters monitor paging, which is the movement of pages of code and data between disk and physical memory. Excessive paging, a symptom of a memory shortage, can cause delays which interfere with all system processes.
6=% Processor Time
7=% Processor Time is the percentage of elapsed time that the processor spends to execute a non-Idle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%. (Each processor has an idle thread that consumes cycles when no other threads are ready to run). This counter is the primary indicator of processor activity, and displays the average percentage of busy time observed during the sample interval. It should be noted that the accounting calculation of whether the processor is idle is performed at an internal sampling interval of the system clock (10ms). On todays fast processors, % Processor Time can therefore underestimate the processor utilization as the processor may be spending a lot of time servicing threads between the system clock sampling interval. Workload based timer applications are one example of applications which are more likely to be measured inaccurately as timers are signaled just after the sample is taken.
9=% Total DPC Time is the average percentage of time that all processors spend receiving and servicing deferred procedure calls (DPCs). (DPCs are interrupts that run at a lower priority than the standard interrupts). It is the sum of Processor: % DPC Time for all processors on the computer, divided by the number of processors. System: % Total DPC Time is a component of System: % Total Privileged Time because DPCs are executed in privileged mode. DPCs are counted separately and are not a component of the interrupt count. This counter displays the average busy time as a percentage of the sample time.
10=File Read Operations/sec
11=File Read Operations/sec is the combined rate of file system read requests to all devices on the computer, including requests to read from the file system cache. It is measured in numbers of reads. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
12=File Write Operations/sec
13=File Write Operations/sec is the combined rate of the file system write requests to all devices on the computer, including requests to write to data in the file system cache. It is measured in numbers of writes. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
14=File Control Operations/sec
15=File Control Operations/sec is the combined rate of file system operations that are neither reads nor writes, such as file system control requests and requests for information about device characteristics or status. This is the inverse of System: File Data Operations/sec and is measured in number of operations perf second. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
16=File Read Bytes/sec
17=File Read Bytes/sec is the overall rate at which bytes are read to satisfy file system read requests to all devices on the computer, including reads from the file system cache. It is measured in number of bytes per second. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
18=File Write Bytes/sec
19=File Write Bytes/sec is the overall rate at which bytes are written to satisfy file system write requests to all devices on the computer, including writes to the file system cache. It is measured in number of bytes per second. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
20=File Control Bytes/sec
21=File Control Bytes/sec is the overall rate at which bytes are transferred for all file system operations that are neither reads nor writes, including file system control requests and requests for information about device characteristics or status. It is measured in numbers of bytes. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
23=% Total Interrupt Time is the average percentage of time that all processors spend receiving and servicing hardware interrupts during sample intervals, where the value is an indirect indicator of the activity of devices that generate interrupts. It is the sum of Processor: % Interrupt Time for of all processors on the computer, divided by the number of processors. DPCs are counted separately and are not a component of the interrupt count. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices.
24=Available Bytes
25=Available Bytes is the amount of physical memory, in bytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.
26=Committed Bytes
27=Committed Bytes is the amount of committed virtual memory, in bytes. Committed memory is the physical memory which has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average.
28=Page Faults/sec
29=Page Faults/sec is the average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation, hence this is also equal to the number of page fault operations. This counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequence. However, hard faults, which require disk access, can cause significant delays.
30=Commit Limit
31=Commit Limit is the amount of virtual memory that can be committed without having to extend the paging file(s). It is measured in bytes. Committed memory is the physical memory which has space reserved on the disk paging files. There can be one paging file on each logical drive). If the paging file(s) are be expanded, this limit increases accordingly. This counter displays the last observed value only; it is not an average.
32=Write Copies/sec
33=Write Copies/sec is the rate at which page faults are caused by attempts to write that have been satisfied by coping of the page from elsewhere in physical memory. This is an economical way of sharing data since pages are only copied when they are written to; otherwise, the page is shared. This counter shows the number of copies, without regard for the number of pages copied in each operation.
34=Transition Faults/sec
35=Transition Faults/sec is the rate at which page faults are resolved by recovering pages that were being used by another process sharing the page, or were on the modified page list or the standby list, or were being written to disk at the time of the page fault. The pages were recovered without additional disk activity. Transition faults are counted in numbers of faults; because only one page is faulted in each operation, it is also equal to the number of pages faulted.
36=Cache Faults/sec
37=Cache Faults/sec is the rate at which faults occur when a page sought in the file system cache is not found and must be retrieved from elsewhere in memory (a soft fault) or from disk (a hard fault). The file system cache is an area of physical memory that stores recently used pages of data for applications. Cache activity is a reliable indicator of most application I/O operations. This counter shows the number of faults, without regard for the number of pages faulted in each operation.
38=Demand Zero Faults/sec
39=Demand Zero Faults/sec is the rate at which a zeroed page is required to satisfy the fault. Zeroed pages, pages emptied of previously stored data and filled with zeros, are a security feature of Windows that prevent processes from seeing data stored by earlier processes that used the memory space. Windows maintains a list of zeroed pages to accelerate this process. This counter shows the number of faults, without regard to the number of pages retrieved to satisfy the fault. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
40=Pages/sec
41=Pages/sec is the rate at which pages are read from or written to disk to resolve hard page faults. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It is the sum of Memory\\Pages Input/sec and Memory\\Pages Output/sec. It is counted in numbers of pages, so it can be compared to other counts of pages, such as Memory\\Page Faults/sec, without conversion. It includes pages retrieved to satisfy faults in the file system cache (usually requested by applications) non-cached mapped memory files.
42=Page Reads/sec
43=Page Reads/sec is the rate at which the disk was read to resolve hard page faults. It shows the number of reads operations, without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in working set or elsewhere in physical memory, and must be retrieved from disk. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\\Pages Reads/sec to the value of Memory\\Pages Input/sec to determine the average number of pages read during each operation.
44=Processor Queue Length
45=Processor Queue Length is the number of threads in the processor queue. Unlike the disk counters, this counter counters, this counter shows ready threads only, not threads that are running. There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. A sustained processor queue of less than 10 threads per processor is normally acceptable, dependent of the workload.
46=Thread State
47=Thread State is the current state of the thread. It is 0 for Initialized, 1 for Ready, 2 for Running, 3 for Standby, 4 for Terminated, 5 for Wait, 6 for Transition, 7 for Unknown. A Running thread is using a processor; a Standby thread is about to use one. A Ready thread wants to use a processor, but is waiting for a processor because none are free. A thread in Transition is waiting for a resource in order to execute, such as waiting for its execution stack to be paged in from disk. A Waiting thread has no use for the processor because it is waiting for a peripheral operation to complete or a resource to become free.
48=Pages Output/sec
49=Pages Output/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written back to disk only if they are changed in physical memory, so they are likely to hold data, not code. A high rate of pages output might indicate a memory shortage. Windows writes more pages back to disk to free up space when physical memory is in short supply. This counter shows the number of pages, and can be compared to other counts of pages, without conversion.
50=Page Writes/sec
51=Page Writes/sec is the rate at which pages are written to disk to free up space in physical memory. Pages are written to disk only if they are changed while in physical memory, so they are likely to hold data, not code. This counter shows write operations, without regard to the number of pages written in each operation. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
52=Browser
53=The Browser performance object consists of counters that measure the rates of announcements, enumerations, and other Browser transmissions.
54=Announcements Server/sec
55=Announcements Server/sec is the rate at which the servers in this domain have announced themselves to this server.
56=Pool Paged Bytes
57=Pool Paged Bytes is the size, in bytes, of the paged pool, an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. Memory\\Pool Paged Bytes is calculated differently than Process\\Pool Paged Bytes, so it might not equal Process(_Total)\\Pool Paged Bytes. This counter displays the last observed value only; it is not an average.
58=Pool Nonpaged Bytes
59=Pool Nonpaged Bytes is the size, in bytes, of the nonpaged pool, an area of the system virtual memory that is used for objects that cannot be written to disk, but must remain in physical memory as long as they are allocated. Memory\\Pool Nonpaged Bytes is calculated differently than Process\\Pool Nonpaged Bytes, so it might not equal Process(_Total)\\Pool Nonpaged Bytes. This counter displays the last observed value only; it is not an average.
60=Pool Paged Allocs
61=Pool Paged Allocs is the number of calls to allocate space in the paged pool. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call. This counter displays the last observed value only; it is not an average.
63=Pool Paged Resident Bytes is the size, in bytes, of the portion of the paged pool that is currently resident and active in physical memory. The paged pool is an area of the system virtual memory that is used for objects that can be written to disk when they are not being used. This counter displays the last observed value only; it is not an average.
64=Pool Nonpaged Allocs
65=Pool Nonpaged Allocs is the number of calls to allocate space in the nonpaged pool. The nonpaged pool is an area of system memory area for objects that cannot be written to disk, and must remain in physical memory as long as they are allocated. It is measured in numbers of calls to allocate space, regardless of the amount of space allocated in each call. This counter displays the last observed value only; it is not an average.
66=Pool Paged Resident Bytes
67=Bytes Total/sec is the total rate of bytes sent to or received from the network by the protocol, but only for the frames (packets) which carry data. This is the sum of Frame Bytes/sec and Datagram Bytes/sec.
68=System Code Total Bytes
69=System Code Total Bytes is the size, in bytes, of the pageable operating system code currently mapped into the system virtual address space. This value is calculated by summing the bytes in Ntoskrnl.exe, Hal.dll, the boot drivers, and file systems loaded by Ntldr/osloader. This counter does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
70=System Code Resident Bytes
71=System Code Resident Bytes is the size, in bytes, of the pageable operating system code that is currently resident and active in physical memory. This value is a component of Memory\\System Code Total Bytes. Memory\\System Code Resident Bytes (and Memory\\System Code Total Bytes) does not include code that must remain in physical memory and cannot be written to disk. This counter displays the last observed value only; it is not an average.
72=System Driver Total Bytes
73=System Driver Total Bytes is the size, in bytes, of the pageable virtual memory currently being used by device drivers. Pageable memory can be written to disk when it is not being used. It includes both physical memory (Memory\\System Driver Resident Bytes) and code and data paged to disk. It is a component of Memory\\System Code Total Bytes. This counter displays the last observed value only; it is not an average.
74=System Driver Resident Bytes
75=System Driver Resident Bytes is the size, in bytes, of the pageable physical memory being used by device drivers. It is the working set (physical memory area) of the drivers. This value is a component of Memory\\System Driver Total Bytes, which also includes driver memory that has been written to disk. Neither Memory\\System Driver Resident Bytes nor Memory\\System Driver Total Bytes includes memory that cannot be written to disk.
76=System Cache Resident Bytes
77=System Cache Resident Bytes is the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The System Cache Resident Bytes and Memory\\Cache Bytes counters are equivalent. This counter displays the last observed value only; it is not an average.
78=Announcements Domain/sec
79=Announcements Domain/sec is the rate at which a domain has announced itself to the network.
80=Election Packets/sec
81=Election Packets/sec is the rate at which browser election packets have been received by this workstation.
82=Mailslot Writes/sec
83=Mailslot Writes/sec is the rate at which mailslot messages have been successfully received.
84=Server List Requests/sec
85=Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this workstation.
86=Cache
87=The Cache performance object consists of counters that monitor the file system cache, an area of physical memory that stores recently used data as long as possible to permit access to the data without having to read from the disk. Because applications typically use the cache, the cache is monitored as an indicator of application I/O operations. When memory is plentiful, the cache can grow, but when memory is scarce, the cache can become too small to be effective.
88=Data Maps/sec
89=Data Maps/sec is the frequency that a file system such as NTFS, maps a page of a file into the file system cache to read the page.
90=Sync Data Maps/sec
91=Sync Data Maps/sec counts the frequency that a file system, such as NTFS, maps a page of a file into the file system cache to read the page, and wishes to wait for the page to be retrieved if it is not in main memory.
92=Async Data Maps/sec
93=Async Data Maps/sec is the frequency that an application using a file system, such as NTFS, to map a page of a file into the file system cache to read the page, and does not wait for the page to be retrieved if it is not in main memory.
94=Data Map Hits %
95=Data Map Hits is the percentage of data maps in the file system cache that could be resolved without having to retrieve a page from the disk, because the page was already in physical memory.
96=Data Map Pins/sec
97=Data Map Pins/sec is the frequency of data maps in the file system cache that resulted in pinning a page in main memory, an action usually preparatory to writing to the file on disk. While pinned, a page's physical address in main memory and virtual address in the file system cache will not be altered.
98=Pin Reads/sec
99=Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. While pinned, a page's physical address in the file system cache will not be altered.
100=Sync Pin Reads/sec
101=Sync Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will not regain control until the page is pinned in the file system cache, in particular if the disk must be accessed to retrieve the page. While pinned, a page's physical address in the file system cache will not be altered.
102=Async Pin Reads/sec
103=Async Pin Reads/sec is the frequency of reading data into the file system cache preparatory to writing the data back to disk. Pages read in this fashion are pinned in memory at the completion of the read. The file system will regain control immediately even if the disk must be accessed to retrieve the page. While pinned, a page's physical address will not be altered.
104=Pin Read Hits %
105=Pin Read Hits is the percentage of pin read requests that hit the file system cache, i.e., did not require a disk read in order to provide access to the page in the file system cache. While pinned, a page's physical address in the file system cache will not be altered. The LAN Redirector uses this method for retrieving data from the cache, as does the LAN Server for small transfers. This is usually the method used by the disk file systems as well.
106=Copy Reads/sec
107=Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the file system cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well.
108=Sync Copy Reads/sec
109=Sync Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The file system will not regain control until the copy operation is complete, even if the disk must be accessed to retrieve the page.
110=Async Copy Reads/sec
111=Async Copy Reads/sec is the frequency of reads from pages of the file system cache that involve a memory copy of the data from the cache to the application's buffer. The application will regain control immediately even if the disk must be accessed to retrieve the page.
112=Copy Read Hits %
113=Copy Read Hits is the percentage of cache copy read requests that hit the cache, that is, they did not require a disk read in order to provide access to the page in the cache. A copy read is a file read operation that is satisfied by a memory copy from a page in the cache to the application's buffer. The LAN Redirector uses this method for retrieving information from the cache, as does the LAN Server for small transfers. This is a method used by the disk file systems as well.
114=MDL Reads/sec
115=MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the data. The MDL contains the physical address of each page involved in the transfer, and thus can employ a hardware Direct Memory Access (DMA) device to effect the copy. The LAN Server uses this method for large transfers out of the server.
116=Sync MDL Reads/sec
117=Sync MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the caller will wait for the pages to fault in from the disk.
118=Async MDL Reads/sec
119=Async MDL Reads/sec is the frequency of reads from the file system cache that use a Memory Descriptor List (MDL) to access the pages. The MDL contains the physical address of each page in the transfer, thus permitting Direct Memory Access (DMA) of the pages. If the accessed page(s) are not in main memory, the calling application program will not wait for the pages to fault in from disk.
120=MDL Read Hits %
121=MDL Read Hits is the percentage of Memory Descriptor List (MDL) Read requests to the file system cache that hit the cache, i.e., did not require disk accesses in order to provide memory access to the page(s) in the cache.
122=Read Aheads/sec
123=Read Aheads/sec is the frequency of reads from the file system cache in which the Cache detects sequential access to a file. The read aheads permit the data to be transferred in larger blocks than those being requested by the application, reducing the overhead per access.
124=Fast Reads/sec
125=Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided.
126=Sync Fast Reads/sec
127=Sync Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests invoke the appropriate file system to retrieve data from a file, but this path permits direct retrieval of data from the cache without file system involvement if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will wait until the data has been retrieved from disk.
128=Async Fast Reads/sec
129=Async Fast Reads/sec is the frequency of reads from the file system cache that bypass the installed file system and retrieve the data directly from the cache. Normally, file I/O requests will invoke the appropriate file system to retrieve data from a file, but this path permits data to be retrieved from the cache directly (without file system involvement) if the data is in the cache. Even if the data is not in the cache, one invocation of the file system is avoided. If the data is not in the cache, the request (application program call) will not wait until the data has been retrieved from disk, but will get control immediately.
130=Fast Read Resource Misses/sec
131=Fast Read Resource Misses/sec is the frequency of cache misses necessitated by the lack of available resources to satisfy the request.
132=Fast Read Not Possibles/sec
133=Fast Read Not Possibles/sec is the frequency of attempts by an Application Program Interface (API) function call to bypass the file system to get to data in the file system cache that could not be honored without invoking the file system.
134=Lazy Write Flushes/sec
135=Lazy Write Flushes/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred by each write operation.
136=Lazy Write Pages/sec
137=Lazy Write Pages/sec is the rate at which the Lazy Writer thread has written to disk. Lazy Writing is the process of updating the disk after the page has been changed in memory, so that the application that changed the file does not have to wait for the disk write to be complete before proceeding. More than one page can be transferred on a single disk write operation.
138=Data Flushes/sec
139=Data Flushes/sec is the rate at which the file system cache has flushed its contents to disk as the result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.
140=Data Flush Pages/sec
141=Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or to satisfy a write-through file write request. More than one page can be transferred on each flush operation.
142=% User Time
143=% User Time is the percentage of elapsed time the processor spends in the user mode. User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems. The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory. The operating system switches application threads to privileged mode to access operating system services. This counter displays the average busy time as a percentage of the sample time.
144=% Privileged Time
145=% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
146=Context Switches/sec
147=Context Switches/sec is the combined rate at which all processors on the computer are switched from one thread to another. Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an Executive or subsystem service. It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches. There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
148=Interrupts/sec
149=Interrupts/sec is the average rate, in incidents per second, at which the processor received and serviced hardware interrupts. It does not include deferred procedure calls (DPCs), which are counted separately. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards, and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended. The system clock typically interrupts the processor every 10 milliseconds, creating a background of interrupt activity. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
150=System Calls/sec
151=System Calls/sec is the combined rate of calls to operating system service routines by all processes running on the computer. These routines perform all of the basic scheduling and synchronization of activities on the computer, and provide access to non-graphic devices, memory management, and name space management. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
152=Level 1 TLB Fills/sec
153=Level 1 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB). On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.
154=Level 2 TLB Fills/sec
155=Level 2 TLB Fills/sec is the frequency of faults that occur when reference is made to memory whose Page Table Entry (PTE) is not in the Translation Lookaside Buffer (TLB), nor is the page containing the PTE. On some computers this fault is handled by software loading the PTE into the TLB, and this counter is incremented.
156=Enumerations Server/sec
157=% User Time is the percentage of elapsed time that the process threads spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the Windows executive, kernel, and device drivers. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
158=Enumerations Domain/sec
159=% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service is called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
160=Enumerations Other/sec
161=Enumerations Server/sec is the rate at which server browse requests have been processed by this workstation.
162=Missed Server Announcements
163=Enumerations Domain/sec is the rate at which domain browse requests have been processed by this workstation.
164=Missed Mailslot Datagrams
165=Enumerations Other/sec is the rate at which browse requests processed by this workstation are not domain or server browse requests.
166=Missed Server List Requests
167=Missed Server Announcements is the number of server announcements that have been missed due to configuration or allocation limits.
168=Server Announce Allocations Failed/sec
169=Missed Mailslot Datagrams is the number of Mailslot Datagrams that have been discarded due to configuration or allocation limits.
170=Mailslot Allocations Failed
171=Missed Server List Requests is the number of requests to retrieve a list of browser servers that were received by this workstation, but could not be processed.
172=Virtual Bytes Peak
173=Virtual Bytes Peak is the maximum size, in bytes, of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. However, virtual space is finite, and the process might limit its ability to load libraries.
174=Virtual Bytes
175=Virtual Bytes is the current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries.
177=Page Faults/sec is the rate at which page faults by the threads executing in this process are occurring. A page fault occurs when a thread refers to a virtual memory page that is not in its working set in main memory. This may not cause the page to be fetched from disk if it is on the standby list and hence already in main memory, or if it is in use by another process with whom the page is shared.
178=Working Set Peak
179=Working Set Peak is the maximum size, in bytes, of the Working Set of this process at any point in time. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before they leave main memory.
180=Working Set
181=Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.
182=Page File Bytes Peak
183=Page File Bytes Peak is the maximum amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the maximum amount of virtual memory that the process has reserved for use in physical memory.
184=Page File Bytes
185=Page File Bytes is the current amount of virtual memory, in bytes, that this process has reserved for use in the paging file(s). Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory. If there is no paging file, this counter reflects the current amount of virtual memory that the process has reserved for use in physical memory.
186=Private Bytes
187=Private Bytes is the current size, in bytes, of memory that this process has allocated that cannot be shared with other processes.
188=Announcements Total/sec
189=% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
190=Enumerations Total/sec
191=% Processor Time is the percentage of elapsed time that all of process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.
193=% User Time is the percentage of elapsed time that this thread has spent executing code in user mode. Applications, environment subsystems, and integral subsystems execute in user mode. Code executing in user mode cannot damage the integrity of the Windows NT Executive, Kernel, and device drivers. Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows NT on behalf of your application might appear in other subsystem processes in addition to the privileged time in your process.
195=% Privileged Time is the percentage of elapsed time that the process threads spent executing code in privileged mode. When a Windows system service in called, the service will often run in privileged mode to gain access to system-private data. Such data is protected from access by threads executing in user mode. Calls to the system can be explicit or implicit, such as page faults or interrupts. Unlike some early operating systems, Windows uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. Some work done by Windows on behalf of the application might appear in other subsystem processes in addition to the privileged time in the process.
197=Context Switches/sec is the rate of switches from one thread to another. Thread switches can occur either inside of a single process or across processes. A thread switch can be caused either by one thread asking another for information, or by a thread being preempted by another, higher priority thread becoming ready to run. Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of user and privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows NT on behalf of an application appear in other subsystem processes in addition to the privileged time in the application. Switching to the subsystem process causes one Context Switch in the application thread. Switching back causes another Context Switch in the subsystem thread.
198=Current Disk Queue Length
199=Current Disk Queue Length is the number of requests outstanding on the disk at the time the performance data is collected. It also includes requests in service at the time of the collection. This is a instantaneous snapshot, not an average over the time interval. Multi-spindle disk devices can have multiple requests that are active at one time, but other concurrent requests are awaiting service. This counter might reflect a transitory high or low queue length, but if there is a sustained load on the disk drive, it is likely that this will be consistently high. Requests experience delays proportional to the length of this queue minus the number of spindles on the disks. For good performance, this difference should average less than two.
200=% Disk Time
201=% Disk Time is the percentage of elapsed time that the selected disk drive was busy servicing read or write requests.
202=% Disk Read Time
203=% Disk Read Time is the percentage of elapsed time that the selected disk drive was busy servicing read requests.
204=% Disk Write Time
205=% Disk Write Time is the percentage of elapsed time that the selected disk drive was busy servicing write requests.
206=Avg. Disk sec/Transfer
207=Avg. Disk sec/Transfer is the time, in seconds, of the average disk transfer.
208=Avg. Disk sec/Read
209=Avg. Disk sec/Read is the average time, in seconds, of a read of data from the disk.
210=Avg. Disk sec/Write
211=Avg. Disk sec/Write is the average time, in seconds, of a write of data to the disk.
212=Disk Transfers/sec
213=Disk Transfers/sec is the rate of read and write operations on the disk.
214=Disk Reads/sec
215=Disk Reads/sec is the rate of read operations on the disk.
216=Disk Writes/sec
217=Disk Writes/sec is the rate of write operations on the disk.
218=Disk Bytes/sec
219=Disk Bytes/sec is the rate bytes are transferred to or from the disk during write or read operations.
220=Disk Read Bytes/sec
221=Disk Read Bytes/sec is the rate at which bytes are transferred from the disk during read operations.
222=Disk Write Bytes/sec
223=Disk Write Bytes/sec is rate at which bytes are transferred to the disk during write operations.
224=Avg. Disk Bytes/Transfer
225=Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations.
226=Avg. Disk Bytes/Read
227=Avg. Disk Bytes/Read is the average number of bytes transferred from the disk during read operations.
228=Avg. Disk Bytes/Write
229=Avg. Disk Bytes/Write is the average number of bytes transferred to the disk during write operations.
230=Process
231=The Process performance object consists of counters that monitor running application program and system processes. All the threads in a process share the same address space and have access to the same data.
232=Thread
233=The Thread performance object consists of counters that measure aspects of thread behavior. A thread is the basic object that executes instructions on a processor. All running processes have at least one thread.
234=PhysicalDisk
235=The Physical Disk performance object consists of counters that monitor hard or fixed disk drive on a computer. Disks are used to store file, program, and paging data and are read to retrieve these items, and written to record changes to them. The values of physical disk counters are sums of the values of the logical disks (or partitions) into which they are divided.
236=LogicalDisk
237=The Logical Disk performance object consists of counters that monitor logical partitions of a hard or fixed disk drives. Performance Monitor identifies logical disks by their a drive letter, such as C.
238=Processor
239=The Processor performance object consists of counters that measure aspects of processor activity. The processor is the part of the computer that performs arithmetic and logical computations, initiates operations on peripherals, and runs the threads of processes. A computer can have multiple processors. The processor object represents each processor as an instance of the object.
240=% Total Processor Time
241=% Total Processor Time is the average percentage of time that all processors on the computer are executing non-idle threads. This counter was designed as the primary indicator of processor activity on multiprocessor computers. It is equal to the sum of Process: % Processor Time for all processors, divided by the number of processors. It is calculated by summing the time that all processors spend executing the thread of the Idle process in each sample interval, subtracting that value from 100%, and dividing the difference by the number of processors on the computer. (Each processor has an Idle thread which consumes cycles when no other threads are ready to run). For example, on a multiprocessor computer, a value of 50% means that all processors are busy for half of the sample interval, or that half of the processors are busy for all of the sample interval. This counter displays the average percentage of busy time observed during the sample interval. It is calculated by monitoring the time the service was inactive, and then subtracting that value from 100%.
242=% Total User Time
243=% Total User Time is the average percentage of non-idle time all processors spend in user mode. It is the sum of Processor: % User Time for all processors on the computer, divided by the number of processors. System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%. (User mode is a restricted processing mode designed for applications, environment subsystems, and integral subsystems. The alternative, privileged mode, is designed for operating system components and allows direct access to hardware and all memory. The operating system switches application threads to privileged mode to access operating system services). This counter displays the average busy time as a percentage of the sample time.
244=% Total Privileged Time
245=% Total Privileged Time is the average percentage of non-idle time all processors spend in privileged (kernel) mode. It is the sum of Processor: % Privileged Time for all processors on the computer, divided by the number of processors. System: % Total User Time and System: % Total Privileged Time sum to % Total Processor Time, but not always to 100%. (Privileged mode is an processing mode designed for operating system components which allows direct access to hardware and all memory. The operating system switches application threads to privileged mode to access operating system services. The alternative, user mode, is a restricted processing mode designed for applications and environment subsystems). This counter displays the average busy time as a percentage of the sample time.
246=Total Interrupts/sec
247=Total Interrupts/sec is the combined rate of hardware interrupts received and serviced by all processors on the computer It is the sum of Processor: Interrupts/sec for all processors, and divided by the number of processors, and is measured in numbers of interrupts. It does not include DPCs, which are counted separately. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system timer, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
248=Processes
249=Processes is the number of processes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. Each process represents the running of a program.
250=Threads
251=Threads is the number of threads in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. A thread is the basic executable entity that can execute instructions in a processor.
252=Events
253=Events is the number of events in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. An event is used when two or more threads try to synchronize execution.
254=Semaphores
255=Semaphores is the number of semaphores in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. Threads use semaphores to obtain exclusive access to data structures that they share with other threads.
256=Mutexes
257=Mutexes counts the number of mutexes in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. Mutexes are used by threads to assure only one thread is executing a particular section of code.
258=Sections
259=Sections is the number of sections in the computer at the time of data collection. This is an instantaneous count, not an average over the time interval. A section is a portion of virtual memory created by a process for storing data. A process can share sections with other processes.
260=Objects
261=The Object performance object consists of counters that monitor logical objects in the system, such as processes, threads, mutexes, and semaphores. This information can be used to detect the unnecessary consumption of computer resources. Each object requires memory to store basic information about the object.
262=Redirector
263=The Redirector performance object consists of counter that monitor network connections originating at the local computer.
264=Bytes Received/sec
265=Bytes Received/sec is the rate of bytes coming in to the Redirector from the network. It includes all application data as well as network protocol information (such as packet headers).
266=Packets Received/sec
267=Packets Received/sec is the rate at which the Redirector is receiving packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes received in a packet can be obtained by dividing Bytes Received/sec by this counter. Some packets received might not contain incoming data (for example an acknowledgment to a write made by the Redirector would count as an incoming packet).
268=Read Bytes Paging/sec
269=Read Bytes Paging/sec is the rate at which the Redirector is attempting to read bytes in response to page faults. Page faults are caused by loading of modules (such as programs and libraries), by a miss in the Cache (see Read Bytes Cache/sec), or by files directly mapped into the address space of applications (a high-performance feature of Windows NT).
270=Read Bytes Non-Paging/sec
271=Read Bytes Non-Paging/sec are those bytes read by the Redirector in response to normal file requests by an application when they are redirected to come from another computer. In addition to file requests, this counter includes other methods of reading across the network such as Named Pipes and Transactions. This counter does not count network protocol information, just application data.
272=Read Bytes Cache/sec
273=Read Bytes Cache/sec is the rate at which applications are accessing the file system cache by using the Redirector. Some of these data requests are satisfied by retrieving the data from the cache. Requests that miss the Cache cause a page fault (see Read Bytes Paging/sec).
274=Read Bytes Network/sec
275=Read Bytes Network/sec is the rate at which applications are reading data across the network. This occurs when data sought in the file system cache is not found there and must be retrieved from the network. Dividing this value by Bytes Received/sec indicates the proportion of application data traveling across the network. (see Bytes Received/sec).
276=Bytes Transmitted/sec
277=Bytes Transmitted/sec is the rate at which bytes are leaving the Redirector to the network. It includes all application data as well as network protocol information (such as packet headers and the like).
278=Packets Transmitted/sec
279=Packets Transmitted/sec is the rate at which the Redirector is sending packets (also called SMBs or Server Message Blocks). Network transmissions are divided into packets. The average number of bytes transmitted in a packet can be obtained by dividing Bytes Transmitted/sec by this counter.
280=Write Bytes Paging/sec
281=Write Bytes Paging/sec is the rate at which the Redirector is attempting to write bytes changed in the pages being used by applications. The program data changed by modules (such as programs and libraries) that were loaded over the network are 'paged out' when no longer needed. Other output pages come from the file system cache (see Write Bytes Cache/sec).
282=Write Bytes Non-Paging/sec
283=Write Bytes Non-Paging/sec is the rate at which bytes are written by the Redirector in response to normal file outputs by an application when they are redirected to another computer. In addition to file requests, this count includes other methods of writing across the network, such as Named Pipes and Transactions. This counter does not count network protocol information, just application data.
284=Write Bytes Cache/sec
285=Write Bytes Cache/sec is the rate at which applications on your computer are writing to the file system cache by using the Redirector. The data might not leave your computer immediately; it can be retained in the cache for further modification before being written to the network. This saves network traffic. Each write of a byte into the cache is counted here.
286=Write Bytes Network/sec
287=Write Bytes Network/sec is the rate at which applications are writing data across the network. This occurs when the file system cache is bypassed, such as for Named Pipes or Transactions, or when the cache writes the bytes to disk to make room for other data. Dividing this counter by Bytes Transmitted/sec will indicate the proportion of application data being to the network (see Transmitted Bytes/sec).
288=Read Operations/sec
289=File Read Operations/sec is the rate at which applications are asking the Redirector for data. Each call to a file system or similar Application Program Interface (API) call counts as one operation.
290=Read Operations Random/sec
291=Read Operations Random/sec counts the rate at which, on a file-by-file basis, reads are made that are not sequential. If a read is made using a particular file handle, and then is followed by another read that is not immediately the contiguous next byte, this counter is incremented by one.
292=Read Packets/sec
293=Read Packets/sec is the rate at which read packets are being placed on the network. Each time a single packet is sent with a request to read data remotely, this counter is incremented by one.
294=Reads Large/sec
295=Reads Large/sec is the rate at which reads over 2 times the server's negotiated buffer size are made by applications. Too many of these could place a strain on server resources. This counter is incremented once for each read. It does not count packets.
296=Read Packets Small/sec
297=Read Packets Small/sec is the rate at which reads less than one-fourth of the server's negotiated buffer size are made by applications. Too many of these could indicate a waste of buffers on the server. This counter is incremented once for each read. It does not count packets.
298=Write Operations/sec
299=File Write Operations/sec is the rate at which applications are sending data to the Redirector. Each call to a file system or similar Application Program Interface (API) call counts as one operation.
300=Write Operations Random/sec
301=Write Operations Random/sec is the rate at which, on a file-by-file basis, writes are made that are not sequential. If a write is made using a particular file handle, and then is followed by another write that is not immediately the next contiguous byte, this counter is incremented by one.
302=Write Packets/sec
303=Write Packets/sec is the rate at which writes are being sent to the network. Each time a single packet is sent with a request to write remote data, this counter is incremented by one.
304=Writes Large/sec
305=Writes Large/sec is the rate at which writes are made by applications that are over 2 times the server's negotiated buffer size. Too many of these could place a strain on server resources. This counter is incremented once for each write: it counts writes, not packets.
306=Write Packets Small/sec
307=Write Packets Small/sec is the rate at which writes are made by applications that are less than one-fourth of the server's negotiated buffer size. Too many of these could indicate a waste of buffers on the server. This counter is incremented once for each write: it counts writes, not packets.
308=Reads Denied/sec
309=Reads Denied/sec is the rate at which the server is unable to accommodate requests for Raw Reads. When a read is much larger than the server's negotiated buffer size, the Redirector requests a Raw Read which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet. To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.
310=Writes Denied/sec
311=Writes Denied/sec is the rate at which the server is unable to accommodate requests for Raw Writes. When a write is much larger than the server's negotiated buffer size, the Redirector requests a Raw Write which, if granted, would permit the transfer of the data without lots of protocol overhead on each packet. To accomplish this the server must lock out other requests, so the request is denied if the server is really busy.
312=Network Errors/sec
313=Network Errors/sec is the rate at which serious unexpected errors are occurring. Such errors generally indicate that the Redirector and one or more Servers are having serious communication difficulties. For example an SMB (Server Message Block) protocol error is a Network Error. An entry is written to the System Event Log and provide details.
314=Server Sessions
315=Server Sessions counts the total number of security objects the Redirector has managed. For example, a logon to a server followed by a network access to the same server will establish one connection, but two sessions.
316=Server Reconnects
317=Server Reconnects counts the number of times your Redirector has had to reconnect to a server in order to complete a new active request. You can be disconnected by the Server if you remain inactive for too long. Locally even if all your remote files are closed, the Redirector will keep your connections intact for (nominally) ten minutes. Such inactive connections are called Dormant Connections. Reconnecting is expensive in time.
318=Connects Core
319=Connects Core counts the number of connections you have to servers running the original MS-Net SMB protocol, including MS-Net itself and Xenix and VAX's.
320=Connects Lan Manager 2.0
321=Connects LAN Manager 2.0 counts connections to LAN Manager 2.0 servers, including LMX servers.
322=Connects Lan Manager 2.1
323=Connects LAN Manager 2.1 counts connections to LAN Manager 2.1 servers, including LMX servers.
324=Connects Windows NT
325=Connects Windows NT counts the connections to Windows 2000 or earlier computers.
326=Server Disconnects
327=Server Disconnects counts the number of times a Server has disconnected your Redirector. See also Server Reconnects.
328=Server Sessions Hung
329=Server Sessions Hung counts the number of active sessions that are timed out and unable to proceed due to a lack of response from the remote server.
330=Server
331=The Server performance object consists of counters that measure communication between the local computer and the network.
333=The number of bytes the server has received from the network. Indicates how busy the server is.
335=The number of bytes the server has sent on the network. Indicates how busy the server is.
336=Thread Wait Reason
337=Thread Wait Reason is only applicable when the thread is in the Wait state (see Thread State). It is 0 or 7 when the thread is waiting for the Executive, 1 or 8 for a Free Page, 2 or 9 for a Page In, 3 or 10 for a Pool Allocation, 4 or 11 for an Execution Delay, 5 or 12 for a Suspended condition, 6 or 13 for a User Request, 14 for an Event Pair High, 15 for an Event Pair Low, 16 for an LPC Receive, 17 for an LPC Reply, 18 for Virtual Memory, 19 for a Page Out; 20 and higher are not assigned at the time of this writing. Event Pairs are used to communicate with protected subsystems (see Context Switches).
339=% DPC Time is the percentage of time that the processor spent receiving and servicing deferred procedure calls (DPCs) during the sample interval. DPCs are interrupts that run at a lower priority than standard interrupts. % DPC Time is a component of % Privileged Time because DPCs are executed in privileged mode. They are counted separately and are not a component of the interrupt counters. This counter displays the average busy time as a percentage of the sample time.
340=Sessions Timed Out
341=The number of sessions that have been closed due to their idle time exceeding the AutoDisconnect parameter for the server. Shows whether the AutoDisconnect setting is helping to conserve resources.
342=Sessions Errored Out
343=The number of sessions that have been closed due to unexpected error conditions or sessions that have reached the autodisconnect timeout and have been disconnected normally. The autodisconnect timeout value represents the number of seconds that idle connections with no session attached to have before being disconnected automatically by a server. The default value is 30 seconds. This counter increments as a result of normal server operation, not as an indication of network problems or unexpected error condition.
344=Sessions Logged Off
345=The number of sessions that have terminated normally. Useful in interpreting the Sessions Times Out and Sessions Errored Out statistics--allows percentage calculations.
346=Sessions Forced Off
347=The number of sessions that have been forced to logoff. Can indicate how many sessions were forced to logoff due to logon time constraints.
348=Errors Logon
349=The number of failed logon attempts to the server. Can indicate whether password guessing programs are being used to crack the security on the server.
350=Errors Access Permissions
351=The number of times opens on behalf of clients have failed with STATUS_ACCESS_DENIED. Can indicate whether somebody is randomly attempting to access files in hopes of getting at something that was not properly protected.
352=Errors Granted Access
353=The number of times accesses to files opened successfully were denied. Can indicate attempts to access files without proper access authorization.
354=Errors System
355=The number of times an internal Server Error was detected. Unexpected errors usually indicate a problem with the Server.
356=Blocking Requests Rejected
357=The number of times the server has rejected blocking SMBs due to insufficient count of free work items. Indicates whether the MaxWorkItem or MinFreeWorkItems server parameters might need to be adjusted.
358=Work Item Shortages
359=The number of times STATUS_DATA_NOT_ACCEPTED was returned at receive indication time. This occurs when no work item is available or can be allocated to service the incoming request. Indicates whether the InitWorkItems or MaxWorkItems parameters might need to be adjusted.
360=Files Opened Total
361=The number of successful open attempts performed by the server of behalf of clients. Useful in determining the amount of file I/O, determining overhead for path-based operations, and for determining the effectiveness of open locks.
362=Files Open
363=The number of files currently opened in the server. Indicates current server activity.
365=The number of sessions currently active in the server. Indicates current server activity.
366=File Directory Searches
367=The number of searches for files currently active in the server. Indicates current server activity.
369=The number of bytes of non-pageable computer memory the server is using. This value is useful for determining the values of the MaxNonpagedMemoryUsage value entry in the Windows NT Registry.
370=Pool Nonpaged Failures
371=The number of times allocations from nonpaged pool have failed. Indicates that the computer's physical memory is too small.
372=Pool Nonpaged Peak
373=The maximum number of bytes of nonpaged pool the server has had in use at any one point. Indicates how much physical memory the computer should have.
375=The number of bytes of pageable computer memory the server is currently using. Can help in determining good values for the MaxPagedMemoryUsage parameter.
376=Pool Paged Failures
377=The number of times allocations from paged pool have failed. Indicates that the computer's physical memory or paging file are too small.
378=Pool Paged Peak
379=The maximum number of bytes of paged pool the server has had allocated. Indicates the proper sizes of the Page File(s) and physical memory.
381=Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory.
383=Mailslot Allocations Failed is the number of times the datagram receiver has failed to allocate a buffer to hold a user mailslot write.
385=Mailslot Receives Failed indicates the number of mailslot messages that could not be received due to transport failures.
387=Mailslot Writes Failed is the total number of mailslot messages that have been successfully received, but that could not be written to the mailslot.
388=Bytes Total/sec
389=Bytes Total/sec is the rate the Redirector is processing data bytes. This includes all application and file data in addition to protocol information such as packet headers.
391=File Data Operations/sec is the rate at which the Redirector is processing data operations. One operation should include many bytes, since each operation has overhead. The efficiency of this path can be determined by dividing the Bytes/sec by this counter to obtain the average number of bytes transferred per operation.
392=Current Commands
393=Current Commands counter indicates the number of pending commands from the local computer to all destination servers. If the Current Commands counter shows a high number and the local computer is idle, this may indicate a network-related problem or a redirector bottleneck on the local computer.
395=The number of bytes the server has sent to and received from the network. This value provides an overall indication of how busy the server is.
397=% Interrupt Time is the time the processor spends receiving and servicing hardware interrupts during sample intervals. This value is an indirect indicator of the activity of devices that generate interrupts, such as the system clock, the mouse, disk drivers, data communication lines, network interface cards and other peripheral devices. These devices normally interrupt the processor when they have completed a task or require attention. Normal thread execution is suspended during interrupts. Most system clocks interrupt the processor every 10 milliseconds, creating a background of interrupt activity. suspends normal thread execution during interrupts. This counter displays the average busy time as a percentage of the sample time.
398=NWLink NetBIOS
399=The NWLink NetBIOS performance object consists of counters that monitor IPX transport rates and connections.
400=Packets/sec
401=Packets/sec is the rate the Redirector is processing data packets. One packet includes (hopefully) many bytes. We say hopefully here because each packet has protocol overhead. You can determine the efficiency of this path by dividing the Bytes/sec by this counter to determine the average number of bytes transferred/packet. You can also divide this counter by Operations/sec to determine the average number of packets per operation, another measure of efficiency.
404=Context Blocks Queued/sec
405=Context Blocks Queued per second is the rate at which work context blocks had to be placed on the server's FSP queue to await server action.
406=File Data Operations/sec
407=File Data Operations/ sec is the combined rate of read and write operations on all logical disks on the computer. This is the inverse of System: File Control Operations/sec. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
408=% Free Space
409=% Free Space is the percentage of total usable space on the selected logical disk drive that was free.
410=Free Megabytes
411=Free Megabytes displays the unallocated space, in megabytes, on the disk drive in megabytes. One megabyte is equal to 1,048,576 bytes.
412=Connections Open
413=Connections Open is the number of connections currently open for this protocol. This counter shows the current count only and does not accumulate over time.
414=Connections No Retries
415=Connections No Retries is the total count of connections that were successfully made on the first try. This number is an accumulator and shows a running total.
416=Connections With Retries
417=Connections With Retries is the total count of connections that were made after retrying the attempt. A retry occurs when the first connection attempt failed. This number is an accumulator and shows a running total.
418=Disconnects Local
419=Disconnects Local is the number of session disconnections that were initiated by the local computer. This number is an accumulator and shows a running total.
420=Disconnects Remote
421=Disconnects Remote is the number of session disconnections that were initiated by the remote computer. This number is an accumulator and shows a running total.
422=Failures Link
423=Failures Link is the number of connections that were dropped due to a link failure. This number is an accumulator and shows a running total.
424=Failures Adapter
425=Failures Adapter is the number of connections that were dropped due to an adapter failure. This number is an accumulator and shows a running total.
426=Connection Session Timeouts
427=Connection Session Timeouts is the number of connections that were dropped due to a session timeout. This number is an accumulator and shows a running total.
428=Connections Canceled
429=Connections Canceled is the number of connections that were canceled. This number is an accumulator and shows a running total.
430=Failures Resource Remote
431=Failures Resource Remote is the number of connections that failed because of resource problems or shortages on the remote computer. This number is an accumulator and shows a running total.
432=Failures Resource Local
433=Failures Resource Local is the number of connections that failed because of resource problems or shortages on the local computer. This number is an accumulator and shows a running total.
434=Failures Not Found
435=Failures Not Found is the number of connection attempts that failed because the remote computer could not be found. This number is an accumulator and shows a running total.
436=Failures No Listen
437=Failures No Listen is the number of connections that were rejected because the remote computer was not listening for connection requests.
438=Datagrams/sec
439=Datagrams/sec is the rate at which datagrams are processed by the computer. This counter displays the sum of datagrams sent and datagrams received. A datagram is a connectionless packet whose delivery to a remote is not guaranteed.
440=Datagram Bytes/sec
441=Datagram Bytes/sec is the rate at which datagram bytes are processed by the computer. This counter is the sum of datagram bytes that are sent as well as received. A datagram is a connectionless packet whose delivery to a remote is not guaranteed.
442=Datagrams Sent/sec
443=Datagrams Sent/sec is the rate at which datagrams are sent from the computer. A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
444=Datagram Bytes Sent/sec
445=Datagram Bytes Sent/sec is the rate at which datagram bytes are sent from the computer. A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
446=Datagrams Received/sec
447=Datagrams Received/sec is the rate at which datagrams are received by the computer. A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
448=Datagram Bytes Received/sec
449=Datagram Bytes Received/sec is the rate at which datagram bytes are received by the computer. A datagram is a connectionless packet whose delivery to a remote computer is not guaranteed.
451=Packets/sec is the rate at which packets are processed by the computer. This count is the sum of Packets Sent and Packets Received per second. This counter includes all packets processed: control as well as data packets.
452=Packets Sent/sec
453=Packets Sent/sec is the rate at which packets are sent by the computer. This counter counts all packets sent by the computer, i.e. control as well as data packets.
455=Packets Received/sec is the rate at which packets are received by the computer. This counter counts all packets processed: control as well as data packets.
456=Frames/sec
457=Frames/sec is the rate at which data frames (or packets) are processed by the computer. This counter is the sum of data frames sent and data frames received. This counter only counts those frames (packets) that carry data.
458=Frame Bytes/sec
459=Frame Bytes/sec is the rate at which data bytes are processed by the computer. This counter is the sum of data frame bytes sent and received. This counter only counts the byte in frames (packets) that carry data.
460=Frames Sent/sec
461=Frames Sent/sec is the rate at which data frames are sent by the computer. This counter only counts the frames (packets) that carry data.
462=Frame Bytes Sent/sec
463=Frame Bytes Sent/sec is the rate at which data bytes are sent by the computer. This counter only counts the bytes in frames (packets) that carry data.
464=Frames Received/sec
465=Frames Received/sec is the rate at which data frames are received by the computer. This counter only counts the frames (packets) that carry data.
466=Frame Bytes Received/sec
467=Frame Bytes Received/sec is the rate at which data bytes are received by the computer. This counter only counts the frames (packets) that carry data.
468=Frames Re-Sent/sec
469=Frames Re-Sent/sec is the rate at which data frames (packets) are re-sent by the computer. This counter only counts the frames or packets that carry data.
470=Frame Bytes Re-Sent/sec
471=Frame Bytes Re-Sent/sec is the rate at which data bytes are re-sent by the computer. This counter only counts the bytes in frames that carry data.
472=Frames Rejected/sec
473=Frames Rejected/sec is the rate at which data frames are rejected. This counter only counts the frames (packets) that carry data.
474=Frame Bytes Rejected/sec
475=Frame Bytes Rejected/sec is the rate at which data bytes are rejected. This counter only counts the bytes in data frames (packets) that carry data.
476=Expirations Response
477=Expirations Response is the count of T1 timer expirations.
478=Expirations Ack
479=Expirations Ack is the count of T2 timer expirations.
480=Window Send Maximum
481=Window Send Maximum is the maximum number of bytes of data that will be sent before waiting for an acknowledgment from the remote computer.
482=Window Send Average
483=Window Send Average is the running average number of data bytes that were sent before waiting for an acknowledgment from the remote computer.
484=Piggyback Ack Queued/sec
485=Piggyback Ack Queued/sec is the rate at which piggybacked acknowledgments are queued. Piggyback acknowledgments are acknowledgments to received packets that are to be included in the next outgoing packet to the remote computer.
486=Piggyback Ack Timeouts
487=Piggyback Ack Timeouts is the number of times that a piggyback acknowledgment could not be sent because there was no outgoing packet to the remote on which to piggyback. A piggyback ack is an acknowledgment to a received packet that is sent along in an outgoing data packet to the remote computer. If no outgoing packet is sent within the timeout period, then an ack packet is sent and this counter is incremented.
488=NWLink IPX
489=The NWLink IPX performance object consists of counters that measure datagram transmission to and from computers using the IPX protocol.
490=NWLink SPX
491=The NWLink SPX performance object consist of counters that measure data transmission and session connections for computers using the SPX protocol.
492=NetBEUI
493=The NetBEUI performance object consists of counters that measure data transmission for network activity which conforms to the NetBIOS End User Interface standard.
494=NetBEUI Resource
495=The NetBEUI Resource performance object consists of counters that track the use of buffers by the NetBEUI protocol.
496=Used Maximum
497=Used Maximum is the maximum number of NetBEUI resources (buffers) in use at any point in time. This value is useful in sizing the maximum resources provided. The number in parentheses following the resource name is used to identify the resource in Event Log messages.
498=Used Average
499=Used Average is the current number of resources (buffers) in use at this time. The number in parentheses following the resource name is used to identify the resource in Event Log messages.
500=Times Exhausted
501=Times Exhausted is the number of times all the resources (buffers) were in use. The number in parentheses following the resource name is used to identify the resource in Event Log messages.
502=NBT Connection
503=The NBT Connection performance object consists of counters that measure the rates at which bytes are sent and received over the NBT connection between the local computer and a remote computer. The connection is identified by the name of the remote computer.
505=Bytes Received/sec is the rate at which bytes are received by the local computer over an NBT connection to some remote computer. All the bytes received by the local computer over the particular NBT connection are counted.
506=Bytes Sent/sec
507=Bytes Sent/sec is the rate at which bytes are sent by the local computer over an NBT connection to some remote computer. All the bytes sent by the local computer over the particular NBT connection are counted.
508=Total Bytes/sec
509=Bytes Total/sec is the rate at which bytes are sent or received by the local computer over an NBT connection to some remote computer. All the bytes sent or received by the local computer over the particular NBT connection are counted.
510=Network Interface
511=The Network Interface performance object consists of counters that measure the rates at which bytes and packets are sent and received over a network connection. It includes counters that monitor connection errors.
512=Bytes/sec
513=Bytes Total/sec is the rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\Bytes Total/sec is a sum of Network Interface\Bytes Received/sec and Network Interface\Bytes Sent/sec.
515=Packets/sec is the rate at which packets are sent and received on the network interface.
517=Packets Received/sec is the rate at which packets are received on the network interface.
519=Packets Sent/sec is the rate at which packets are sent on the network interface.
520=Current Bandwidth
521=Current Bandwidth is an estimate of the current bandwidth of the network interface in bits per second (BPS). For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth.
523=Bytes Received/sec is the rate at which bytes are received over each network adapter, including framing characters. Network Interface\Bytes Received/sec is a subset of Network Interface\Bytes Total/sec.
524=Packets Received Unicast/sec
525=Packets Received Unicast/sec is the rate at which (subnet) unicast packets are delivered to a higher-layer protocol.
526=Packets Received Non-Unicast/sec
527=Packets Received Non-Unicast/sec is the rate at which non-unicast (subnet broadcast or subnet multicast) packets are delivered to a higher-layer protocol.
528=Packets Received Discarded
529=Packets Received Discarded is the number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their delivery to a higher-layer protocol. One possible reason for discarding packets could be to free up buffer space.
530=Packets Received Errors
531=Packets Received Errors is the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
532=Packets Received Unknown
533=Packets Received Unknown is the number of packets received through the interface that were discarded because of an unknown or unsupported protocol.
535=Bytes Sent/sec is the rate at which bytes are sent over each network adapter, including framing characters. Network Interface\Bytes Sent/sec is a subset of Network Interface\Bytes Total/sec.
536=Packets Sent Unicast/sec
537=Packets Sent Unicast/sec is the rate at which packets are requested to be transmitted to subnet-unicast addresses by higher-level protocols. The rate includes the packets that were discarded or not sent.
538=Packets Sent Non-Unicast/sec
539=Packets Sent Non-Unicast/sec is the rate at which packets are requested to be transmitted to non-unicast (subnet broadcast or subnet multicast) addresses by higher-level protocols. The rate includes the packets that were discarded or not sent.
540=Packets Outbound Discarded
541=Packets Outbound Discarded is the number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent transmission. One possible reason for discarding packets could be to free up buffer space.
542=Packets Outbound Errors
543=Packets Outbound Errors is the number of outbound packets that could not be transmitted because of errors.
544=Output Queue Length
545=Output Queue Length is the length of the output packet queue (in packets). If this is longer than two, there are delays and the bottleneck should be found and eliminated, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0.
546=IPv4
547=The IP performance object consists of counters that measure the rates at which IP datagrams are sent and received by using IP protocols. It also includes counters that monitor IP protocol errors.
548=IPv6
549=Datagrams/sec is the rate, in incidents per second, at which IP datagrams were received from or sent to the interfaces, including those in error. Forwarded datagrams are not included in this rate.
551=Datagrams Received/sec is the rate, in incidents per second, at which IP datagrams are received from the interfaces, including those in error. Datagrams Received/sec is a subset of Datagrams/sec.
552=Datagrams Received Header Errors
553=Datagrams Received Header Errors is the number of input datagrams that were discarded due to errors in the IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
554=Datagrams Received Address Errors
555=Datagrams Received Address Errors is the number of input datagrams that were discarded because the IP address in their IP header destination field was not valid for the computer. This count includes invalid addresses (for example, 0.0. 0.0) and addresses of unsupported Classes (for example, Class E). For entities that are not IP gateways and do not forward datagrams, this counter includes datagrams that were discarded because the destination address was not a local address.
556=Datagrams Forwarded/sec
557=Datagrams Forwarded/sec is the rate, in incidents per second, at which attemps were made to find routes to forward input datagrams their final destination, because the local server was not the final IP destination. In servers that do not act as IP Gateways, this rate includes only packets that were source-routed via this entity, where the source-route option processing was successful.
558=Datagrams Received Unknown Protocol
559=Datagrams Received Unknown Protocol is the number of locally-addressed datagrams that were successfully received but were discarded because of an unknown or unsupported protocol.
560=Datagrams Received Discarded
561=Datagrams Received Discarded is the number of input IP datagrams that were discarded even though problems prevented their continued processing (for example, lack of buffer space). This counter does not include any datagrams discarded while awaiting re-assembly.
562=Datagrams Received Delivered/sec
563=Datagrams Received Delivered/sec is the rate, in incidents per second, at which input datagrams were successfully delivered to IP user-protocols, including Internet Control Message Protocol (ICMP).
565=Datagrams Sent/sec is the rate, in incidents per second, at which IP datagrams were supplied for transmission by local IP user-protocols (including ICMP). This counter does not include any datagrams counted in Datagrams Forwarded/sec. Datagrams Sent/sec is a subset of Datagrams/sec.
566=Datagrams Outbound Discarded
567=Datagrams Outbound Discarded is the number of output IP datagrams that were discarded even though no problems were encountered to prevent their transmission to their destination (for example, lack of buffer space). This counter includes datagrams counted in Datagrams Forwarded/sec that meet this criterion.
568=Datagrams Outbound No Route
569=Datagrams Outbound No Route is the number of IP datagrams that were discarded because no route could be found to transmit them to their destination. This counter includes any packets counted in Datagrams Forwarded/sec that meet this `no route' criterion.
570=Fragments Received/sec
571=Fragments Received/sec is the rate, in incidents per second, at which IP fragments that need to be reassembled at this entity are received.
572=Fragments Re-assembled/sec
573=Fragments Re-assembled/sec is the rate, in incidents per second, at which IP fragments were successfully reassembled.
574=Fragment Re-assembly Failures
575=Fragment Re-assembly Failures is the number of failures detected by the IP reassembly algorithm, such as time outs, errors, etc. This is not necessarily a count of discarded IP fragments since some algorithms (notably RFC 815) lose track of the number of fragments by combining them as they are received.
576=Fragmented Datagrams/sec
577=Fragmented Datagrams/sec is the rate, in incidents per second, at which datagrams are successfully fragmented.
578=Fragmentation Failures
579=Fragmentation Failures is the number of IP datagrams that were discarded because they needed to be fragmented at but could not be (for example, because the `Don't Fragment' flag was set).
580=Fragments Created/sec
581=Fragments Created/sec is the rate, in incidents per second, at which IP datagram fragments were generated as a result of fragmentation.
582=ICMP
583=The ICMP performance object consists of counters that measure the rates at which messages are sent and received by using ICMP protocols. It also includes counters that monitor ICMP protocol errors.
584=Messages/sec
585=Messages/sec is the total rate, in incidents per second, at which ICMP messages were sent and received by the entity. The rate includes messages received or sent in error.
586=Messages Received/sec
587=Messages Received/sec is the rate, in incidents per second at which ICMP messages were received. The rate includes messages received in error.
588=Messages Received Errors
589=Messages Received Errors is the number of ICMP messages that the entity received but had errors, such as bad ICMP checksums, bad length, etc.
590=Received Dest. Unreachable
591=Received Destination Unreachable is the number of ICMP Destination Unreachable messages received.
592=Received Time Exceeded
593=Received Time Exceeded is the number of ICMP Time Exceeded messages received.
594=Received Parameter Problem
595=Received Parameter Problem is the number of ICMP Parameter Problem messages received.
596=Received Source Quench
597=Received Source Quench is the number of ICMP Source Quench messages received.
598=Received Redirect/sec
599=Received Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were received.
600=Received Echo/sec
601=Received Echo/sec is the rate, in incidents per second, at which ICMP Echo messages were received.
602=Received Echo Reply/sec
603=Received Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were received.
604=Received Timestamp/sec
605=Received Timestamp/sec is the rate, in incidents per second at which ICMP Timestamp Request messages were received.
606=Received Timestamp Reply/sec
607=Received Timestamp Reply/sec is the rate of ICMP Timestamp Reply messages received.
608=Received Address Mask
609=Received Address Mask is the number of ICMP Address Mask Request messages received.
610=Received Address Mask Reply
611=Received Address Mask Reply is the number of ICMP Address Mask Reply messages received.
612=Messages Sent/sec
613=Messages Sent/sec is the rate, in incidents per second, at which the server attempted to send. The rate includes those messages sent in error.
614=Messages Outbound Errors
615=Messages Outbound Errors is the number of ICMP messages that were not send due to problems within ICMP, such as lack of buffers. This value does not include errors discovered outside the ICMP layer, such as those recording the failure of IP to route the resultant datagram. In some implementations, none of the error types are included in the value of this counter.
616=Sent Destination Unreachable
617=Sent Destination Unreachable is the number of ICMP Destination Unreachable messages sent.
618=Sent Time Exceeded
619=Sent Time Exceeded is the number of ICMP Time Exceeded messages sent.
620=Sent Parameter Problem
621=Sent Parameter Problem is the number of ICMP Parameter Problem messages sent.
622=Sent Source Quench
623=Sent Source Quench is the number of ICMP Source Quench messages sent.
624=Sent Redirect/sec
625=Sent Redirect/sec is the rate, in incidents per second, at which ICMP Redirect messages were sent.
626=Sent Echo/sec
627=Sent Echo/sec is the rate of ICMP Echo messages sent.
628=Sent Echo Reply/sec
629=Sent Echo Reply/sec is the rate, in incidents per second, at which ICMP Echo Reply messages were sent.
630=Sent Timestamp/sec
631=Sent Timestamp/sec is the rate, in incidents per second, at which ICMP Timestamp Request messages were sent.
632=Sent Timestamp Reply/sec
633=Sent Timestamp Reply/sec is the rate, in incidents per second, at which ICMP Timestamp Reply messages were sent.
634=Sent Address Mask
635=Sent Address Mask is the number of ICMP Address Mask Request messages sent.
636=Sent Address Mask Reply
637=Sent Address Mask Reply is the number of ICMP Address Mask Reply messages sent.
638=TCPv4
639=The TCP performance object consists of counters that measure the rates at which TCP Segments are sent and received by using the TCP protocol. It includes counters that monitor the number of TCP connections in each TCP connection state.
640=Segments/sec
641=Segments/sec is the rate at which TCP segments are sent or received using the TCP protocol.
642=Connections Established
643=Connections Established is the number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
644=Connections Active
645=Connections Active is the number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state. In other words, it shows a number of connections which are initiated by the local computer. The value is a cumulative total.
646=Connections Passive
647=Connections Passive is the number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state. In other words, it shows a number of connections to the local computer, which are initiated by remote computers. The value is a cumulative total.
648=Connection Failures
649=Connection Failures is the number of times TCP connections have made a direct transition to the CLOSED state from the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
650=Connections Reset
651=Connections Reset is the number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
652=Segments Received/sec
653=Segments Received/sec is the rate at which segments are received, including those received in error. This count includes segments received on currently established connections.
654=Segments Sent/sec
655=Segments Sent/sec is the rate at which segments are sent, including those on current connections, but excluding those containing only retransmitted bytes.
656=Segments Retransmitted/sec
657=Segments Retransmitted/sec is the rate at which segments are retransmitted, that is, segments transmitted containing one or more previously transmitted bytes.
658=UDPv4
659=The UDP performance object consists of counters that measure the rates at which UDP datagrams are sent and received by using the UDP protocol. It includes counters that monitor UDP protocol errors.
660=% Total DPC Time
661=Datagrams/sec is the rate at which UDP datagrams are sent or received by the entity.
662=% Total Interrupt Time
663=Datagrams Received/sec is the rate at which UDP datagrams are delivered to UDP users.
664=Datagrams No Port/sec
665=Datagrams No Port/sec is the rate of received UDP datagrams for which there was no application at the destination port.
666=Datagrams Received Errors
667=Datagrams Received Errors is the number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
669=Datagrams Sent/sec is the rate at which UDP datagrams are sent from the entity.
670=Disk Storage Unit
671=Disk Storage device statistics from the foreign computer
672=Allocation Failures
673=The number of allocation failures reported by the disk storage device
674=System Up Time
675=System Up Time is the elapsed time (in seconds) that the computer has been running since it was last started. This counter displays the difference between the start time and the current time.
676=System Handle Count
677=The current number of system handles in use.
678=Free System Page Table Entries
679=Free System Page Table Entries is the number of page table entries not currently in used by the system. This counter displays the last observed value only; it is not an average.
680=Thread Count
681=The number of threads currently active in this process. An instruction is the basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread.
682=Priority Base
683=The current base priority of this process. Threads within a process can raise and lower their own base priority relative to the process' base priority.
684=Elapsed Time
685=The total elapsed time, in seconds, that this process has been running.
686=Alignment Fixups/sec
687=Alignment Fixups/sec is the rate, in incidents per seconds, at alignment faults were fixed by the system.
688=Exception Dispatches/sec
689=Exception Dispatches/sec is the rate, in incidents per second, at which exceptions were dispatched by the system.
690=Floating Emulations/sec
691=Floating Emulations/sec is the rate of floating emulations performed by the system. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
692=Logon/sec
693=Logon/sec is the rate of all server logons.
694=Priority Current
695=The current dynamic priority of this thread. The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.
696=% DPC Time
697=The current base priority of this thread. The system can raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.
698=% Interrupt Time
699=The total elapsed time (in seconds) this thread has been running.
700=Paging File
701=The Paging File performance object consists of counters that monitor the paging file(s) on the computer. The paging file is a reserved space on disk that backs up committed physical memory on the computer.
702=% Usage
703=The amount of the Page File instance in use in percent. See also Process\\Page File Bytes.
704=% Usage Peak
705=The peak usage of the Page File instance in percent. See also Process\\Page File Bytes Peak.
706=Start Address
707=Starting virtual address for this thread.
708=User PC
709=Current User Program Counter for this thread.
710=Mapped Space No Access
711=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
712=Mapped Space Read Only
713=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Read Only protection prevents the contents of these pages from being modified. Any attempts to write or modify these pages will generate an access violation.
714=Mapped Space Read/Write
715=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Read/Write protection allows a process to read, modify and write to these pages.
716=Mapped Space Write Copy
717=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Write Copy protection is used when memory is shared for reading but not for writing. When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have write access to this shared memory, a copy of that memory is made.
718=Mapped Space Executable
719=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Executable memory is memory that can be executed by programs, but cannot be read or written. This type of protection is not supported by all processor types.
720=Mapped Space Exec Read Only
721=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Execute/Read Only memory is memory that can be executed as well as read.
722=Mapped Space Exec Read/Write
723=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.
724=Mapped Space Exec Write Copy
725=Mapped Space is virtual memory that has been mapped to a specific virtual address (or range of virtual addresses) in the process' virtual address space. Execute Write Copy is memory that can be executed by programs as well as read and written. This type of protection is used when memory needs to be shared between processes. If the sharing processes only read the memory, then they will all use the same memory. If a sharing process desires write access, then a copy of this memory will be made for that process.
726=Reserved Space No Access
727=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
728=Reserved Space Read Only
729=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Read Only protection prevents the contents of these pages from being modified. Any attempts to write or modify these pages will generate an access violation.
730=Reserved Space Read/Write
731=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Read/Write protection allows a process to read, modify and write to these pages.
732=Reserved Space Write Copy
733=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Write Copy protection is used when memory is shared for reading but not for writing. When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made.
734=Reserved Space Executable
735=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Executable memory is memory that can be executed by programs, but cannot be read or written. This type of protection is not supported by all processor types.
736=Reserved Space Exec Read Only
737=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Execute/Read Only memory is memory that can be executed as well as read.
738=Reserved Space Exec Read/Write
739=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Execute/Read/Write memory is memory that can be executed by programs as well as read and modified.
740=Image
741=The Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer.
742=Reserved Space Exec Write Copy
743=Reserved Space is virtual memory that has been reserved for future use by a process, but has not been mapped or committed. Execute Write Copy is memory that can be executed by programs as well as read and written. This type of protection is used when memory needs to be shared between processes. If the sharing processes only read the memory, then they will all use the same memory. If a sharing process desires write access, then a copy of this memory will be made for that process.
744=Unassigned Space No Access
745=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
746=Unassigned Space Read Only
747=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Read Only protection prevents the contents of these pages from being modified. Any attempts to write or modify these pages will generate an access violation.
748=Unassigned Space Read/Write
749=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Read/Write protection allows a process to read, modify and write to these pages.
750=Unassigned Space Write Copy
751=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Write Copy protection is used when memory is shared for reading but not for writing. When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
752=Unassigned Space Executable
753=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Executable memory is memory that can be executed by programs, but cannot be read or written. This type of protection is not supported by all processor types.
754=Unassigned Space Exec Read Only
755=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Execute/Read Only memory is memory that can be executed as well as read.
756=Unassigned Space Exec Read/Write
757=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Execute/Read/Write memory is memory that can be executed by programs as well as read and written.
758=Unassigned Space Exec Write Copy
759=Unassigned Space is mapped and committed virtual memory in use by the process that is not attributable to any particular image being executed by that process. Execute Write Copy is memory that can be executed by programs as well as read and written. This type of protection is used when memory needs to be shared between processes. If the sharing processes only read the memory, then they will all use the same memory. If a sharing process desires write access, then a copy of this memory will be made for that process.
760=Image Space No Access
761=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process No Access protection prevents a process from writing to or reading from these pages and will generate an access violation if either is attempted.
762=Image Space Read Only
763=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Read Only protection prevents the contents of these pages from being modified. Any attempts to write or modify these pages will generate an access violation.
764=Image Space Read/Write
765=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Read/Write protection allows a process to read, modify and write to these pages.
766=Image Space Write Copy
767=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Write Copy protection is used when memory is shared for reading but not for writing. When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
768=Image Space Executable
769=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Executable memory is memory that can be executed by programs, but cannot be read or written. This type of protection is not supported by all processor types.
770=Image Space Exec Read Only
771=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Execute/Read-Only memory is memory that can be executed as well as read.
772=Image Space Exec Read/Write
773=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Execute/Read/Write memory is memory that can be executed by programs as well as read and written and modified.
774=Image Space Exec Write Copy
775=Image Space is the virtual address space in use by the images being executed by the process. This is the sum of all the address space with this protection allocated by images run by the selected process Execute Write Copy is memory that can be executed by programs as well as read and written. This type of protection is used when memory needs to be shared between processes. If the sharing processes only read the memory, then they will all use the same memory. If a sharing process desires write access, then a copy of this memory will be made for that process.
776=Bytes Image Reserved
777=Bytes Image Reserved is the sum of all virtual memory reserved by images within this process.
778=Bytes Image Free
779=Bytes Image Free is the amount of virtual address space that is not in use or reserved by images within this process.
780=Bytes Reserved
781=Bytes Reserved is the total amount of virtual memory reserved for future use by this process.
782=Bytes Free
783=Bytes Free is the total unused virtual address space of this process.
784=ID Process
785=ID Process is the unique identifier of this process. ID Process numbers are reused, so they only identify a process for the lifetime of that process.
786=Process Address Space
787=The Process Address Space performance object consists of counters that monitor memory allocation and use for a selected process.
788=No Access
789=Image Space is the virtual address space in use by the selected image with this protection. No Access protection prevents a process from writing or reading these pages and will generate an access violation if either is attempted.
790=Read Only
791=Image Space is the virtual address space in use by the selected image with this protection. Read Only protection prevents the contents of these pages from being modified. Any attempts to write or modify these pages will generate an access violation.
792=Read/Write
793=Image Space is the virtual address space in use by the selected image with this protection. Read/Write protection allows a process to read, modify and write to these pages.
794=Write Copy
795=Image Space is the virtual address space in use by the selected image with this protection. Write Copy protection is used when memory is shared for reading but not for writing. When processes are reading this memory, they can share the same memory, however, when a sharing process wants to have read/write access to this shared memory, a copy of that memory is made for writing to.
796=Executable
797=Image Space is the virtual address space in use by the selected image with this protection. Executable memory is memory that can be executed by programs, but cannot be read or written. This type of protection is not supported by all processor types.
798=Exec Read Only
799=Image Space is the virtual address space in use by the selected image with this protection. Execute/Read Only memory is memory that can be executed as well as read.
800=Exec Read/Write
801=Image Space is the virtual address space in use by the selected image with this protection. Execute/Read/Write memory is memory that can be executed by programs as well as read and written.
802=Exec Write Copy
803=Image Space is the virtual address space in use by the selected image with this protection. Execute Write Copy is memory that can be executed by programs as well as read and written. This type of protection is used when memory needs to be shared between processes. If the sharing processes only read the memory, then they will all use the same memory. If a sharing process desires write access, then a copy of this memory will be made for that process.
804=ID Thread
805=ID Thread is the unique identifier of this thread. ID Thread numbers are reused, so they only identify a thread for the lifetime of that thread.
806=Mailslot Receives Failed
807=Mailslot Opens Failed/sec indicates the rate at which mailslot messages to be delivered to mailslots that are not present are received by this workstation.
808=Mailslot Writes Failed
809=Duplicate Master Announcements indicates the number of times that the master browser has detected another master browser on the same domain.
810=Mailslot Opens Failed/sec
811=Illegal Datagrams/sec is the rate at which incorrectly formatted datagrams have been received by the workstation.
812=Duplicate Master Announcements
813=Announcements Total/sec is the sum of Announcements Server/sec and Announcements Domain/sec.
814=Illegal Datagrams/sec
815=Enumerations Total/sec is the rate at which browse requests have been processed by this workstation. This is the sum of Enumerations Server/sec, Enumerations Domain/sec, and Enumerations Other/sec.
816=Thread Details
817=The Thread Details performance object consists of counters that measure aspects of thread behavior that are difficult or time-consuming or collect. These counters are distinguished from those in the Thread object by their high overhead.
818=Cache Bytes
819=Cache Bytes the size, in bytes, of the portion of the system file cache which is currently resident and active in physical memory. The Cache Bytes and Memory\\System Cache Resident Bytes counters are equivalent. This counter displays the last observed value only; it is not an average.
820=Cache Bytes Peak
821=Cache Bytes Peak is the maximum number of bytes used by the system file cache since the system was last restarted. This might be larger than the current size of the cache. This counter displays the last observed value only; it is not an average.
822=Pages Input/sec
823=Pages Input/sec is the rate at which pages are read from disk to resolve hard page faults. Hard page faults occur when a process refers to a page in virtual memory that is not in its working set or elsewhere in physical memory, and must be retrieved from disk. When a page is faulted, the system tries to read multiple contiguous pages into memory to maximize the benefit of the read operation. Compare the value of Memory\\Pages Input/sec to the value of Memory\\Page Reads/sec to determine the average number of pages read into memory during each read operation.
824=Transition Pages RePurposed/sec
825=Transition Pages RePurposed is the rate at which the number of transition cache pages were reused for a different purpose. These pages would have otherwise remained in the page cache to provide a (fast) soft fault (instead of retrieving it from backing store) in the event the page was accessed in the future. Note these pages can contain private or sharable memory.
872=Bytes Transmitted
873=The number of bytes transmitted total for this connection.
874=Bytes Received
875=The number of bytes received total for this connection.
876=Frames Transmitted
877=The number of data frames transmitted total for this connection.
878=Frames Received.
879=The number of data frames received total for this connection.
880=Percent Compression Out
881=The compression ratio for bytes being transmitted.
882=Percent Compression In
883=The compression ratio for bytes being received.
884=CRC Errors
885=The total number of CRC Errors for this connection. CRC Errors occur when the frame received contains erroneous data.
886=Timeout Errors
887=The total number of Timeout Errors for this connection. Timeout Errors occur when an expected is not received in time.
888=Serial Overrun Errors
889=The total number of Serial Overrun Errors for this connection. Serial Overrun Errors occur when the hardware cannot handle the rate at which data is received.
890=Alignment Errors
891=The total number of Alignment Errors for this connection. Alignment Errors occur when a byte received is different from the byte expected.
892=Buffer Overrun Errors
893=The total number of Buffer Overrun Errors for this connection. Buffer Overrun Errors when the software cannot handle the rate at which data is received.
894=Total Errors
895=The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors for this connection.
896=Bytes Transmitted/Sec
897=The number of bytes transmitted per second.
898=Bytes Received/Sec
899=The number of bytes received per second.
900=Frames Transmitted/Sec
901=The number of frames transmitted per second.
902=Frames Received/Sec
903=The number of frames received per second.
904=Total Errors/Sec
905=The total number of CRC, Timeout, Serial Overrun, Alignment, and Buffer Overrun Errors per second.
908=Total Connections
909=The total number of Remote Access connections.
920=WINS Server
921=The WINS Server performance object consists of counters that monitor communications using the WINS Server service.
922=Unique Registrations/sec
923=Unique Registrations/sec is the rate at which unique registration are received by the WINS server.
924=Group Registrations/sec
925=Group Registrations/sec is the rate at which group registration are received by the WINS server.
926=Total Number of Registrations/sec
927=Total Number of Registrations/sec is the sum of the Unique and Group registrations per sec. This is the total rate at which registration are received by the WINS server.
928=Unique Renewals/sec
929=Unique Renewals/sec is the rate at which unique renewals are received by the WINS server.
930=Group Renewals/sec
931=Group Renewals/sec is the rate at which group renewals are received by the WINS server.
932=Total Number of Renewals/sec
933=Total Number of Renewals/sec is the sum of the Unique and Group renewals per sec. This is the total rate at which renewals are received by the WINS server.
934=Releases/sec
935=Total Number of Releases/sec is the rate at which releases are received by the WINS server.
936=Queries/sec
937=Total Number of Queries/sec is the rate at which queries are received by the WINS server.
938=Unique Conflicts/sec
939=Unique Conflicts/sec is the rate at which unique registrations/renewals received by the WINS server resulted in conflicts with records in the database.
940=Group Conflicts/sec
941=Group Conflicts/sec is the rate at which group registration received by the WINS server resulted in conflicts with records in the database.
942=Total Number of Conflicts/sec
943=Total Number of Conflicts/sec is the sum of the Unique and Group conflicts per sec. This is the total rate at which conflicts were seen by the WINS server.
944=Successful Releases/sec
945=Total Number of Successful Releases/sec
946=Failed Releases/sec
947=Total Number of Failed Releases/sec
948=Successful Queries/sec
949=Total Number of Successful Queries/sec
950=Failed Queries/sec
951=Total Number of Failed Queries/sec
952=Handle Count
953=The total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in this process.
1000=MacFile Server
1001=Services for Macintosh AFP File Server.
1002=Max Paged Memory
1003=The maximum amount of paged memory resources used by the MacFile Server.
1004=Current Paged Memory
1005=The current amount of paged memory resources used by the MacFile Server.
1006=Max NonPaged Memory
1007=The maximum amount of nonpaged memory resources use by the MacFile Server.
1008=Current NonPaged memory
1009=The current amount of nonpaged memory resources used by the MacFile Server.
1010=Current Sessions
1011=The number of sessions currently connected to the MacFile server. Indicates current server activity.
1012=Maximum Sessions
1013=The maximum number of sessions connected at one time to the MacFile server. Indicates usage level of server.
1014=Current Files Open
1015=The number of internal files currently open in the MacFile server. This count does not include files opened on behalf of Macintosh clients.
1016=Maximum Files Open
1017=The maximum number of internal files open at one time in the MacFile server. This count does not include files opened on behalf of Macintosh clients.
1018=Failed Logons
1019=The number of failed logon attempts to the MacFile server. Can indicate whether password guessing programs are being used to crack the security on the server.
1020=Data Read/sec
1021=The number of bytes read from disk per second.
1022=Data Written/sec
1023=The number of bytes written to disk per second.
1024=Data Received/sec
1025=The number of bytes received from the network per second. Indicates how busy the server is.
1026=Data Transmitted/sec
1027=The number of bytes sent on the network per second. Indicates how busy the server is.
1028=Current Queue Length
1029=The number of outstanding work items waiting to be processed.
1030=Maximum Queue Length
1031=The maximum number of outstanding work items waiting at one time.
1032=Current Threads
1033=The current number of threads used by MacFile server. Indicates how busy the server is.
1034=Maximum Threads
1035=The maximum number of threads used by MacFile server. Indicates peak usage level of server.
1050=AppleTalk
1051=AppleTalk Protocol
1052=Packets In/sec
1053=Number of packets received per second by Appletalk on this port.
1054=Packets Out/sec
1055=Number of packets sent per second by Appletalk on this port.
1056=Bytes In/sec
1057=Number of bytes received per second by Appletalk on this port.
1058=Bytes Out/sec
1059=Number of bytes sent per second by Appletalk on this port.
1060=Average Time/DDP Packet
1061=Average time in milliseconds to process a DDP packet on this port.
1062=DDP Packets/sec
1063=Number of DDP packets per second received by Appletalk on this port.
1064=Average Time/AARP Packet
1065=Average time in milliseconds to process an AARP packet on this port.
1066=AARP Packets/sec
1067=Number of AARP packets per second received by Appletalk on this port.
1068=Average Time/ATP Packet
1069=Average time in milliseconds to process an ATP packet on this port.
1070=ATP Packets/sec
1071=Number of ATP packets per second received by Appletalk on this port.
1072=Average Time/NBP Packet
1073=Average time in milliseconds to process an NBP packet on this port.
1074=NBP Packets/sec
1075=Number of NBP packets per second received by Appletalk on this port.
1076=Average Time/ZIP Packet
1077=Average time in milliseconds to process a ZIP packet on this port.
1078=ZIP Packets/sec
1079=Number of ZIP packets per second received by Appletalk on this port.
1080=Average Time/RTMP Packet
1081=Average time in milliseconds to process an RTMP packet on this port.
1082=RTMP Packets/sec
1083=Number of RTMP packets per second received by Appletalk on this port.
1084=ATP Retries Local
1085=Number of ATP requests retransmitted on this port.
1086=ATP Response Timouts
1087=Number of ATP release timers that have expired on this port.
1088=ATP XO Response/Sec
1089=Number of ATP Exactly-once transaction responses per second on this port.
1090=ATP ALO Response/Sec
1091=Number of ATP At-least-once transaction responses per second on this port.
1092=ATP Recvd Release/Sec
1093=Number of ATP transaction release packets per second received on this port.
1094=Current NonPaged Pool
1095=The current amount of nonpaged memory resources used by AppleTalk.
1096=Packets Routed In/Sec
1097=Number of packets routed in on this port.
1098=Packets dropped
1099=Number of packets dropped due to resource limitations on this port.
1100=ATP Retries Remote
1101=Number of ATP requests retransmitted to this port.
1102=Packets Routed Out/Sec
1103=Number of packets routed out on this port.
1110=Network Segment
1111=Provides Network Statistics for the local network segment via the Network Monitor Service.
1112=Total frames received/second
1113=The total number of frames received per second on this network segment.
1114=Total bytes received/second
1115=The number of bytes received per second on this network segment.
1116=Broadcast frames received/second
1117=The number of Broadcast frames received per second on this network segment.
1118=Multicast frames received/second
1119=The number of Multicast frames received per second on this network segment.
1120=% Network utilization
1121=Percentage of network bandwidth in use on this network segment.
1124=% Broadcast Frames
1125=Percentage of network bandwidth which is made up of broadcast traffic on this network segment.
1126=% Multicast Frames
1127=Percentage of network bandwidth which is made up of multicast traffic on this network segment.
1150=Telephony
1151=The Telephony System
1152=Lines
1153=The number of telephone lines serviced by this computer.
1154=Telephone Devices
1155=The number of telephone devices serviced by this computer.
1156=Active Lines
1157=The number of telephone lines serviced by this computer that are currently active.
1158=Active Telephones
1159=The number of telephone devices that are currently being monitored.
1160=Outgoing Calls/sec
1161=The rate of outgoing calls made by this computer.
1162=Incoming Calls/sec
1163=The rate of incoming calls answered by this computer.
1164=Client Apps
1165=The number of applications that are currently using telephony services.
1166=Current Outgoing Calls
1167=Current outgoing calls being serviced by this computer.
1168=Current Incoming Calls
1169=Current incoming calls being serviced by this computer.
1232=Packet Burst Read NCP Count/sec
1233=Packet Burst Read NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Read. Packet Burst is a windowing protocol that improves performance.
1234=Packet Burst Read Timeouts/sec
1235=Packet Burst Read Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Read Request because the NetWare server took too long to respond.
1236=Packet Burst Write NCP Count/sec
1237=Packet Burst Write NCP Count/sec is the rate of NetWare Core Protocol requests for Packet Burst Write. Packet Burst is a windowing protocol that improves performance.
1238=Packet Burst Write Timeouts/sec
1239=Packet Burst Write Timeouts/sec is the rate the NetWare Service needs to retransmit a Burst Write Request because the NetWare server took too long to respond.
1240=Packet Burst IO/sec
1241=Packet Burst IO/sec is the sum of Packet Burst Read NCPs/sec and Packet Burst Write NCPs/sec.
1260=Logon Total
1261=Logon Total indicates the total session setup attempts, including all successful logon and failed logons since the server service is started.
1262=Total Durable Handles
1263=The total number of durable handle disconnects that have occurred.
1264=Reconnected Durable Handles
1265=The total number of durable handles that are successfully reconnected. The ratio of "reconnected durable handles"/"total durable handles" indicates the stability gain from reconnect durable handles.
1266=SMB BranchCache Hash Header Requests
1267=The number of SMB BranchCache hash requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.
1268=SMB BranchCache Hash Generation Requests
1269=The number of SMB BranchCache hash generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.
1270=SMB BranchCache Hash Requests Received
1271=The number of SMB BranchCache hash requests that were received by the server.
1272=SMB BranchCache Hash Responses Sent
1273=The number of SMB BranchCache hash responses that have been sent from the server.
1274=SMB BranchCache Hash Bytes Sent
1275=The amount of SMB BranchCache hash data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.
1276=Total Resilient Handles
1277=The total number of resilient handle disconnect that have occurred.
1278=Reconnected Resilient Handles
1279=The total number of resilient handles that are successfully reconnected. The ratio of "reconnected resilient handles"/"total resilient handles" indicates the stability gain from reconnect resilient handles.
1300=Server Work Queues
1301=The Server Work Queues performance object consists of counters that monitor the length of the queues and objects in the queues.
1302=Queue Length
1303=Queue length is the current number of workitem in Blocking queues and Nonblocking queues, which indicates how busy the server is to process outstanding workitems for this CPU. A sustained queue length greater than four might indicate processor congestion. This is an instantaneous count, not an average over time.
1304=Active Threads
1305=Active Threads is the number of threads currently working on a request from the server client for this CPU. The system keeps this number as low as possible to minimize unnecessary context switching. This is an instantaneous count for the CPU, not an average over time.
1306=Available Threads
1307=Available Threads is the number of server threads on this CPU not currently working on requests from a client. The server dynamically adjusts the number of threads to maximize server performance.
1308=Available Work Items
1309=Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing. This is the instantaneous number of available work items for this CPU. A sustained near-zero value indicates the need to increase the MinFreeWorkItems registry value for the Server service. This value will always be 0 in the SMB1 Blocking Queue instance.
1310=Borrowed Work Items
1311=Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing. When a CPU runs out of work items, it borrows a free work item from another CPU. An increasing value of this running counter might indicate the need to increase the 'MaxWorkItems' or 'MinFreeWorkItems' registry values for the Server service. This value will always be 0 in the Blocking Queue and SMB2 Queue instances.
1312=Work Item Shortages
1313=Every request from a client is represented in the server as a 'work item,' and the server maintains a pool of available work items per CPU to speed processing. A sustained value greater than zero indicates the need to increase the 'MaxWorkItems' registry value for the Server service. This value will always be 0 in the Blocking Queue and SMB2 Queue instances.
1314=Current Clients
1315=Current Clients is the instantaneous count of the clients being serviced by this CPU. The server actively balances the client load across all of the CPU's in the system. This value will always be 0 in the Blocking Queue instance.
1317=The rate at which the Server is receiving bytes from the network clients on this CPU. This value is a measure of how busy the Server is.
1319=The rate at which the Server is sending bytes to the network clients on this CPU. This value is a measure of how busy the Server is.
1320=Bytes Transferred/sec
1321=The rate at which the Server is sending and receiving bytes with the network clients on this CPU. This value is a measure of how busy the Server is.
1323=Read Operations/sec is the rate the server is performing file read operations for the clients on this CPU. This value is a measure of how busy the Server is. This value will always be 0 in the Blocking Queue instance.
1324=Read Bytes/sec
1325=Read Bytes/sec is the rate the server is reading data from files for the clients on this CPU. This value is a measure of how busy the Server is.
1327=Write Operations/sec is the rate the server is performing file write operations for the clients on this CPU. This value is a measure of how busy the Server is. This value will always be 0 in the Blocking Queue instance.
1328=Write Bytes/sec
1329=Write Bytes/sec is the rate the server is writing data to files for the clients on this CPU. This value is a measure of how busy the Server is.
1331=Total Bytes/sec is the rate the Server is reading and writing data to and from the files for the clients on this CPU. This value is a measure of how busy the Server is.
1332=Total Operations/sec
1333=Total Operations/sec is the rate the Server is performing file read and file write operations for the clients on this CPU. This value is a measure of how busy the Server is. This value will always be 0 in the Blocking Queue instance.
1334=DPCs Queued/sec
1335=DPCs Queued/sec is the average rate, in incidents per second, at which deferred procedure calls (DPCs) were added to the processor's DPC queue. DPCs are interrupts that run at a lower priority than standard interrupts. Each processor has its own DPC queue. This counter measures the rate that DPCs are added to the queue, not the number of DPCs in the queue. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
1336=DPC Rate
1337=DPC Rate is the rate at which deferred procedure calls (DPCs) were added to the processors DPC queues between the timer ticks of the processor clock. DPCs are interrupts that run at alower priority than standard interrupts. Each processor has its own DPC queue. This counter measures the rate that DPCs were added to the queue, not the number of DPCs in the queue. This counter displays the last observed value only; it is not an average.
1342=Total DPCs Queued/sec
1343=Total DPCs Queued/sec is the combined rate at which deferred procedure calls (DPCs) are added to the DPC queue of all processors on the computer. (DPCs are interrupts that run at a lower priority than standard interrupts). Each processor has its own DPC queue. This counter measures the rate at which DPCs are added to the queue, not the number of DPCs in the queue. It is the sum of Processor: DPCs Queued/sec for all processors on the computer, divided by the number of processors. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
1344=Total DPC Rate
1345=Total DPC Rate is the combined rate at which deferred procedure calls (DPCs) are added to the DPC queues of all processors between timer ticks of each processor's system clock. (DPCs are interrupts that run at a lower priority than standard interrupts). Each processor has its own DPC queue. This counter measures the rate at which DPCs are added to the queue, not the number of DPCs in the queue. It is the sum of Processor: DPC Rate for all processors on the computer, divided by the number of processors. This counter displays the last observed value only; it is not an average.
1350=% Registry Quota In Use
1351=% Registry Quota In Use is the percentage of the Total Registry Quota Allowed that is currently being used by the system. This counter displays the current percentage value only; it is not an average.
1360=VL Memory
1361=Counters that indicate the status of local and system Very Large memory allocations.
1362=VLM % Virtual Size In Use
1363=VLM % Virtual Size In Use
1364=VLM Virtual Size
1365=Current size of the process VLM Virtual memory space in bytes.
1366=VLM Virtual Size Peak
1367=The peak size of the process VLM virtual memory space in bytes. This value indicates the maximum size of the process VLM virtual memory since the process started.
1368=VLM Virtual Size Available
1369=The current size of the process VLM virtual memory space in bytes that may be allocated. Note that the maximum allocation allowed may be smaller than this value due to fragmentation of the memory space.
1370=VLM Commit Charge
1371=The current size of committed VLM memory space for the current process in bytes.
1372=VLM Commit Charge Peak
1373=The peak size of the committed VLM memory space in bytes for the current process since the process started.
1374=System VLM Commit Charge
1375=The current size of all committed VLM memory space in bytes for the system.
1376=System VLM Commit Charge Peak
1377=The peak size of all committed VLM memory space in bytes since the system was started.
1378=System VLM Shared Commit Charge
1379=The current size of all committed shared VLM memory space in bytes for the system.
1380=Available KBytes
1381=Available KBytes is the amount of physical memory, in Kilobytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.
1382=Available MBytes
1383=Available MBytes is the amount of physical memory, in Megabytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free and zero page lists.
1400=Avg. Disk Queue Length
1401=Avg. Disk Queue Length is the average number of both read and write requests that were queued for the selected disk during the sample interval.
1402=Avg. Disk Read Queue Length
1403=Avg. Disk Read Queue Length is the average number of read requests that were queued for the selected disk during the sample interval.
1404=Avg. Disk Write Queue Length
1405=Avg. Disk Write Queue Length is the average number of write requests that were queued for the selected disk during the sample interval.
1406=% Committed Bytes In Use
1407=% Committed Bytes In Use is the ratio of Memory\\Committed Bytes to the Memory\\Commit Limit. Committed memory is the physical memory in use for which space has been reserved in the paging file should it need to be written to disk. The commit limit is determined by the size of the paging file. If the paging file is enlarged, the commit limit increases, and the ratio is reduced). This counter displays the current percentage value only; it is not an average.
1408=Full Image
1409=The Full Image performance object consists of counters that monitor the virtual address usage of images executed by processes on the computer. Full Image counters are the same counters as contained in Image object with the only difference being the instance name. In the Full Image object, the instance name includes the full file path name of the loaded modules, while in the Image object only the filename is displayed.
1410=Creating Process ID
1411=The Creating Process ID value is the Process ID of the process that created the process. The creating process may have terminated, so this value may no longer identify a running process.
1412=IO Read Operations/sec
1413=The rate at which the process is issuing read I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1414=IO Write Operations/sec
1415=The rate at which the process is issuing write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1416=IO Data Operations/sec
1417=The rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1418=IO Other Operations/sec
1419=The rate at which the process is issuing I/O operations that are neither read nor write operations (for example, a control function). This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1420=IO Read Bytes/sec
1421=The rate at which the process is reading bytes from I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1422=IO Write Bytes/sec
1423=The rate at which the process is writing bytes to I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1424=IO Data Bytes/sec
1425=The rate at which the process is reading and writing bytes in I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1426=IO Other Bytes/sec
1427=The rate at which the process is issuing bytes to I/O operations that do not involve data such as control operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.
1450=Print Queue
1451=Displays performance statistics about a Print Queue.
1452=Total Jobs Printed
1453=Total number of jobs printed on a print queue since the last restart.
1454=Bytes Printed/sec
1455=Number of bytes per second printed on a print queue.
1456=Total Pages Printed
1457=Total number of pages printed through GDI on a print queue since the last restart.
1458=Jobs
1459=Current number of jobs in a print queue.
1460=References
1461=Current number of references (open handles) to this printer.
1462=Max References
1463=Peak number of references (open handles) to this printer.
1464=Jobs Spooling
1465=Current number of spooling jobs in a print queue.
1466=Max Jobs Spooling
1467=Maximum number of spooling jobs in a print queue since last restart.
1468=Out of Paper Errors
1469=Total number of out of paper errors in a print queue since the last restart.
1470=Not Ready Errors
1471=Total number of printer not ready errors in a print queue since the last restart.
1472=Job Errors
1473=Total number of job errors in a print queue since last restart.
1474=Enumerate Network Printer Calls
1475=Total number of calls from browse clients to this print server to request network browse lists since last restart.
1476=Add Network Printer Calls
1477=Total number of calls from other print servers to add shared network printers to this server since last restart.
1478=Working Set - Private
1479=Working Set - Private displays the size of the working set, in bytes, that is use for this process only and not shared nor sharable by other processes.
1480=Working Set - Shared
1481=Working Set - Shared displays the size of the working set, in bytes, that is sharable and may be used by other processes. Because a portion of a process' working set is shareable, does not necessarily mean that other processes are using it.
1482=% Idle Time
1483=% Idle Time reports the percentage of time during the sample interval that the disk was idle.
1484=Split IO/Sec
1485=Split IO/Sec reports the rate at which I/Os to the disk were split into multiple I/Os. A split I/O may result from requesting data of a size that is too large to fit into a single I/O or that the disk is fragmented.
1500=Job Object
1501=Reports the accounting and processor usage data collected by each active named Job object.
1502=Current % Processor Time
1503=Current % Processor Time shows the percentage of the sample interval that the processes in the Job object spent executing code.
1504=Current % User Mode Time
1505=Current % User mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in user mode.
1506=Current % Kernel Mode Time
1507=Current % Kernel mode Time shows the percentage of the sample interval that the processes in the Job object spent executing code in kernel or privileged mode.
1508=This Period mSec - Processor
1509=This Period mSec - Processor shows the time, in milliseconds, of processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.
1510=This Period mSec - User Mode
1511=This Period mSec - User mode shows the time, in milliseconds, of user mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.
1512=This Period mSec - Kernel Mode
1513=This Period mSec - Kernel mode shows the time, in milliseconds, of kernel mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since a time limit on the Job was established.
1514=Pages/Sec
1515=Pages/Sec shows the page fault rate of all the processes in the Job object.
1516=Process Count - Total
1517=Process Count - Total shows the number of processes, both active and terminated, that are or have been associated with the Job object.
1518=Process Count - Active
1519=Process Count - Active shows the number of processes that are currently associated with the Job object.
1520=Process Count - Terminated
1521=Process Count - Terminated shows the number of processes that have been terminated because of a limit violation.
1522=Total mSec - Processor
1523=Total mSec - Processor shows the time, in milliseconds, of processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.
1524=Total mSec - User Mode
1525=Total mSec - User mode shows the time, in milliseconds, of user mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.
1526=Total mSec - Kernel Mode
1527=Total mSec - Kernel mode shows the time, in milliseconds, of kernel mode processor time used by all the processes in the Job object, including those that have terminated or that are no longer associated with the Job object, since the Job object was created.
1530=TCPv6
1532=UDPv6
1534=ICMPv6
1536=Received Packet Too Big
1537=Received Packet Too Big is the number of received packets thatare larger than anticipated.
1538=Received Membership Query
1539=Received Membership Query is the number of packets received thatquery their membership to a group.
1540=Received Membership Report
1541=Received Membership Report is the number of packets received thatreport their membership to a group.
1542=Received Membership Reduction
1543=Received Membership Reduction is the number of packets received thatcancelled their membership to a group.
1544=Received Router Solicit
1545=Received Router Solicit is the number of packets received thatsolicit the router.
1546=Received Router Advert
1547=Received Router Advert is the number of packets received thatadvert the router.
1548=Job Object Details
1549=% Job object Details shows detailed performance information about the active processes that make up a Job object.
1550=Received Neighbor Solicit
1551=Received Neighbor Solicit is the number of packets received thatsolicit a neighbor.
1552=Received Neighbor Advert
1553=Received Neighbor Advert is the number of packets received thatadvert a neighbor.
1554=Sent Packet Too Big
1555=Sent Packet Too Big is the number of sent packets thatare larger than anticipated.
1556=Sent Membership Query
1557=Sent Membership Query is the number of packets sent thatquery their membership to a group.
1558=Sent Membership Report
1559=Sent Membership Report is the number of packets sent thatreport their membership to a group.
1560=Sent Membership Reduction
1561=Sent Membership Reduction is the number of packets sent thatcancelled their membership to a group.
1562=Sent Router Solicit
1563=Sent Router Solicit is the number of packets sent thatsolicit the router.
1564=Sent Router Advert
1565=Sent Router Advert is the number of packets sent thatadvert the router.
1566=Sent Neighbor Solicit
1567=Sent Neighbor Solicit is the number of packets sent thatsolicit a neighbor.
1568=Sent Neighbor Advert
1569=Sent Neighbor Advert is the number of packets sent thatadvert a neighbor.
1570=Security System-Wide Statistics
1571=These counters track authentication performance on a per second basis.
1572=NTLM Authentications
1573=This counter tracks the number of NTLM authentications processed per second for the AD on this DC or for local accounts on this member server.
1574=Kerberos Authentications
1575=This counter tracks the number of times that clients use a ticket to authenticate to this computer per second.
1576=KDC AS Requests
1577=This counter tracks the number of Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use AS requests to obtain a ticket-granting ticket.
1578=KDC TGS Requests
1579=This counter tracks the number of ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second. Clients use these TGS requests to obtain a service ticket, which allows a client to access resources on other computers.
1580=Schannel Session Cache Entries
1581=This counter tracks the number of Secure Sockets Layer (SSL) entries that are currently stored in the secure channel (Schannel) session cache. The Schannel session cache stores information about successfully established sessions, such as SSL session IDs. Clients can use this information to reconnect to a server without performing a full SSL handshake.
1582=Active Schannel Session Cache Entries
1583=This counter tracks the number of Secure Sockets Layer (SSL) entries that are currently stored in the secure channel (Schannel) session cache and that are currently in use. The Schannel session cache stores information about successfully established sessions, such as SSL session IDs. Clients can use this information to reconnect to a server without performaing a full SSL handshake.
1584=SSL Client-Side Full Handshakes
1585=This counter tracks the number of Secure Sockets Layer (SSL) full client-side handshakes that are being processed per second. During a handshake, signals are exchanged to acknowledge that communication can occur between computers or other devices.
1586=SSL Client-Side Reconnect Handshakes
1587=This counter tracks the number of Secure Sockets Layer (SSL) client-side reconnect handshakes that are being processed per second. Reconnect handshakes allow session keys from previous SSL sessions to be used to resume a client/server connection, and they require less memory to process than full handshakes.
1588=SSL Server-Side Full Handshakes
1589=This counter tracks the number of Secure Sockets Layer (SSL) full server-side handshakes that are being processed per second. During a handshake, signals are exchanged to acknowledge that communication can occur between computers or other devices.
1590=SSL Server-Side Reconnect Handshakes
1591=This counter tracks the number of Secure Sockets Layer (SSL) server-side reconnect handshakes that are being processed per second. Reconnect handshakes allow session keys from previous SSL sessions to be used to resume a client/server connection, and they require less memory to process than full handshakes.
1592=Digest Authentications
1593=This counter tracks the number of Digest authentications that are being processed per second.
1594=Forwarded Kerberos Requests
1595=This counter tracks the number of Kerberos requests that a read-only domain controller (RODC) forwards to its hub, per second. This counter is tracked only on a RODC.
1596=Offloaded Connections
1597=Offloaded Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently handled by the TCP chimney offload capable network adapter.
1598=TCP Active RSC Connections
1599=TCP Active RSC Connections is the number of TCP connections (over both IPv4 and IPv6) that are currently receiving large packets from the RSC capable network adapter on this network interface.
1600=TCP RSC Coalesced Packets/sec
1601=TCP RSC Coalesced Packets/sec shows the large packet receive rate across all TCP connections on this network interface.
1602=TCP RSC Exceptions/sec
1603=TCP RSC Exceptions/sec shows the RSC exception rate for receive packets across all TCP connections on this network interface.
1604=TCP RSC Average Packet Size
1605=TCP RSC Average Packet Size is the average size in bytes of received packets across all TCP connections on this network interface.
1620=KDC armored AS Requests
1621=This counter tracks the number of armored Authentication Service (AS) requests that are being processed by the Key Distribution Center (KDC) per second.
1622=KDC armored TGS Requests
1623=This counter tracks the number of armored ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second.
1624=KDC claims-aware AS Requests
1625=This counter tracks the number of Authentication Service (AS) requests explicitly requesting claims that are being processed by the Key Distribution Center (KDC) per second.
1626=KDC claims-aware service asserted identity TGS requests
1627=This counter tracks the number of service asserted identity (S4U2Self) TGS requests that are explicitly requesting claims. These requests are being processed by the Key Distribution Center (KDC) per second.
1628=KDC classic type constrained delegation TGS Requests
1629=This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking classic type constrained delegation configuration per second. The classic type constrained delegation is restricted to a single domain and configures the backend services SPN on the middle-tier service’s account object.
1630=KDC resource type constrained delegation TGS Requests
1631=This counter tracks the number of constrained delegation (S4U2Proxy) TGS requests that are being processed by the Key Distribution Center (KDC) by checking the resource type constrained delegation per second. The resource type constrained delegation can cross domain boundaries and configures the middle-tier’s account on the backend service’s account object.
1632=KDC claims-aware TGS Requests
1633=This counter tracks the number of claims-aware ticket-granting service (TGS) requests that are being processed by the Key Distribution Center (KDC) per second. A claims-aware Kerberos client will always request claims during Authentication Service (AS) exchanges.
1670=Security Per-Process Statistics
1671=These counters track the number of security resources and handles used per process.
1672=Credential Handles
1673=This counter tracks the number of credential handles in use by a given process. Credential handles are handles to pre-existing credentials, such as a password, that are associated with a user and are established through a system logon.
1674=Context Handles
1675=This counter tracks the number of context handles in use by a given process. Context handles are associated with security contexts established between a client application and a remote peer.
1676=Free & Zero Page List Bytes
1677=Free & Zero Page List Bytes is the amount of physical memory, in bytes, that is assigned to the free and zero page lists. This memory does not contain cached data. It is immediately available for allocation to a process or for system use.
1678=Modified Page List Bytes
1679=Modified Page List Bytes is the amount of physical memory, in bytes, that is assigned to the modified page list. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. This memory needs to be written out before it will be available for allocation to a process or for system use.
1680=Standby Cache Reserve Bytes
1681=Standby Cache Reserve Bytes is the amount of physical memory, in bytes, that is assigned to the reserve standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.
1682=Standby Cache Normal Priority Bytes
1683=Standby Cache Normal Priority Bytes is the amount of physical memory, in bytes, that is assigned to the normal priority standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.
1684=Standby Cache Core Bytes
1685=Standby Cache Core Bytes is the amount of physical memory, in bytes, that is assigned to the core standby cache page lists. This memory contains cached data and code that is not actively in use by processes, the system and the system cache. It is immediately available for allocation to a process or for system use. If the system runs out of available free and zero memory, memory on lower priority standby cache page lists will be repurposed before memory on higher priority standby cache page lists.
1686=Long-Term Average Standby Cache Lifetime (s)
1687=Long-Term Average Standby Cache Lifetime, in seconds. The average lifetime of data in the standby cache over a long interval is measured.
1746=% Idle Time
1747=% Idle Time is the percentage of time the processor is idle during the sample interval
1748=% C1 Time
1749=% C1 Time is the percentage of time the processor spends in the C1 low-power idle state. % C1 Time is a subset of the total processor idle time. C1 low-power idle state enables the processor to maintain its entire context and quickly return to the running state. Not all systems support the % C1 state.
1750=% C2 Time
1751=% C2 Time is the percentage of time the processor spends in the C2 low-power idle state. % C2 Time is a subset of the total processor idle time. C2 low-power idle state enables the processor to maintain the context of the system caches. The C2 power state is a lower power and higher exit latency state than C1. Not all systems support the C2 state.
1752=% C3 Time
1753=% C3 Time is the percentage of time the processor spends in the C3 low-power idle state. % C3 Time is a subset of the total processor idle time. When the processor is in the C3 low-power idle state it is unable to maintain the coherency of its caches. The C3 power state is a lower power and higher exit latency state than C2. Not all systems support the C3 state.
1754=C1 Transitions/sec
1755=C1 Transitions/sec is the rate that the CPU enters the C1 low-power idle state. The CPU enters the C1 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
1756=C2 Transitions/sec
1757=C2 Transitions/sec is the rate that the CPU enters the C2 low-power idle state. The CPU enters the C2 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
1758=C3 Transitions/sec
1759=C3 Transitions/sec is the rate that the CPU enters the C3 low-power idle state. The CPU enters the C3 state when it is sufficiently idle and exits this state on any interrupt. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval.
1760=Heap
1761=Heap performance counters for must used heaps
1762=Committed Bytes
1763=Memory actively used by this heap (FreeBytes + AllocatedBytes)
1764=Reserved Bytes
1765=Total virtual address space reserved for this heap (includes uncommitted ranges)
1766=Virtual Bytes
1767=ReservedBytes minus last uncommitted range in each segment
1768=Free Bytes
1769=Memory on freelists in this heap (does not include uncommitted ranges or blocks in heap cache)
1770=Free List Length
1771=Number of blocks on the list of free blocks >1k in size
1772=Avg. alloc rate
1773=1/Average time per allocation (excluding allocs from heap cache)
1774=Avg. free rate
1775=1/Average time per free (excluding frees to heap cache)
1776=Uncommitted Ranges Length
1777=Number of uncommitted ranges in the reserved virtual address
1778=Allocs - Frees
1779=Difference between number of allocations and frees (for leak detection)
1780=Cached Allocs/sec
1781=Allocations/sec from heap cache
1782=Cached Frees/sec
1783=Frees/sec from heap cache
1784=Allocs <1K/sec
1785=Allocations/sec of size <1k bytes (including heap cache)
1786=Frees <1K/sec
1787=Frees/sec of size <1k bytes (including heap cache)
1788=Allocs 1-8K/sec
1789=Allocations/sec of size 1-8k bytes
1790=Frees 1-8K/sec
1791=Frees/sec of size 1-8k bytes
1792=Allocs over 8K/sec
1793=Allocations/sec of size over 8k bytes
1794=Frees over 8K/sec
1795=Frees/sec of size over 8k bytes
1796=Total Allocs/sec
1797=Allocations/sec (including from heap cache)
1798=Total Frees/sec
1799=Frees/sec (including to heap cache)
1800=Blocks in Heap Cache
1801=Total number of blocks in the heap cache
1802=Largest Cache Depth
1803=Largest number of blocks of any one size in the heap cache
1804=% Fragmentation
1805=(FreeBytes / CommittedBytes) *100
1806=% VAFragmentation
1807=(VirtualBytes / ReservedBytes) * 100
1808=Heap Lock contention
1809=Collisions/sec on the heap lock
1810=Dirty Pages
1811=Total number of dirty pages on the system cache
1812=Dirty Page Threshold
1813=Threshold for number of dirty pages on system cache
1814=NUMA Node Memory
1815=Counters that report approximate memory utilization statistics per node on NUMA systems.
1816=Total MBytes
1817=Total amount of physical memory associated with a NUMA node in megabytes.
1818=Free & Zero Page List MBytes
1819=Approximate amount of physical memory on the free and zero page lists for a NUMA node, in megabytes.
1820=Network Adapter
1821=The Network Adapter performance object consists of counters that measure the rates at which bytes and packets are sent and received over a physical or virtual network connection. It includes counters that monitor connection errors.
1822=Standby List MBytes
1823=Approximate amount of physical memory on the standby page list for a NUMA node, in megabytes. This counter is available only on 64-bit systems.
1824=Available MBytes
1825=Approximate amount of physical memory available for allocation for a NUMA node, in megabytes. Computed as the sum of memory on the zeroed, free, and standby lists for a NUMA node. This counter is available only on 64-bit systems.
1826=SMB BranchCache Hash V2 Header Requests
1827=The number of SMB BranchCache hash V2 requests that were for the header only received by the server. This indicates how many requests are being done to validate hashes that are already cached by the client.
1828=SMB BranchCache Hash V2 Generation Requests
1829=The number of SMB BranchCache hash V2 generation requests that were sent by SRV2 to the SMB Hash Generation service because a client requested hashes for the file and there was either no hash content for the file or the existing hashes were out of date.
1830=SMB BranchCache Hash V2 Requests Received
1831=The number of SMB BranchCache hash V2 requests that were received by the server.
1832=SMB BranchCache Hash V2 Responses Sent
1833=The number of SMB BranchCache hash V2 responses that have been sent from the server.
1834=SMB BranchCache Hash V2 Bytes Sent
1835=The amount of SMB BranchCache hash V2 data sent from the server. This includes bytes transferred for both hash header requests and full hash data requests.
1836=SMB BranchCache Hash V2 Requests Served From Dedup
1837=The amount of SMB BranchCache hash V2 requests that were served from dedup store by the server.
1846=End Marker
1847=End Marker
1900=Telephony
1901=The Telphony System
1902=Number of Lines
1903=The number of telephone lines serviced by this computer.
1904=Number of Telephone devices
1905=The number of telephone devices serviced by this computer.
1906=Number of Active Lines
1907=the number of telephone lines serviced by this computer that are currently active.
1908=Number of Active Telephones
1909=The number of telephone devices that are currently being monitored.
1910=Outgoing calls/sec
1911=The rate of outgoing calls made by this computer.
1912=Incoming calls/sec
1913=The rate of incoming calls answered by this computer.
1914=Number of Client Apps
1915=The number of applications that are currently using telephony services.
1916=Current Outgoing Calls
1917=Current outgoing calls being serviced by this computer.
1918=Current Incoming Calls
1919=Current incoming calls being serviced by this computer.
2020=Search Gatherer Projects
2021=Counters for the Windows Search Service Gatherer Project object
2022=Document Additions
2023=The number of add notifications.
2024=Document Add Rate
2025=The number of document additions per second.
2026=Document Deletes
2027=The number of delete notifications.
2028=Document Delete Rate
2029=The number of document deletes per second.
2030=Document Modifies
2031=The number of modify notifications.
2032=Document Modifies Rate
2033=The number of modify notifications per second.
2034=Waiting Documents
2035=The number of documents waiting to be processed. When this number goes to zero the catalog is idle. This number indicates the total queue size of unprocessed documents in the gatherer.
2036=Documents In Progress
2037=The number of documents in progress.
2038=Documents On Hold
2039=The number of documents on hold because a document with the same URL is currently in process.
2040=Delayed Documents
2041=The number of documents delayed due to site hit frequency rules.
2042=URLs in History
2043=The number of files (URLs) in the history list. This indicates the total size of your document corpus that was indexed.
2044=Processed Documents
2045=The number of documents processed since the history has been reset.
2046=Processed Documents Rate
2047=The number of documents processed per second.
2048=Status Success
2049=The number of successfully filtered documents.
2050=Success Rate
2051=The number of successfully filtered documents per second.
2052=Status Error
2053=The number of filtered documents which returned an error.
2054=Error Rate
2055=The number of filtered documents which returned an error per second.
2060=File Errors
2061=The number of file protocol errors received while getting documents.
2062=File Errors Rate
2063=The number of file protocol errors received per second.
2068=Accessed Files
2069=The number of documents accessed via file system.
2070=Accessed File Rate
2071=The number of documents accessed via file system per second.
2076=Filtered Office
2077=The number of office documents filtered.
2078=Filtered Office Rate
2079=The number of office documents filtered per second.
2080=Filtered Text
2081=The number of text documents filtered.
2082=Filtered Text Rate
2083=The number of text documents filtered per second.
2084=Crawls in progress
2085=Number of crawls in progress.
2086=Gatherer Paused Flag
2087=The Gatherer paused flag indicates if the Gatherer has been paused.
2088=Recovery In Progress Flag
2089=The recovery in progress flag indicates if recovery is currently in progress. Indexing will not be resumed until this flag is off.
2090=Not Modified
2091=The number of documents which were not filtered because no modification was detected since the last crawl.
2092=Iterating History In Progress Flag
2093=The Iterating history in progress flag indicates if the Gatherer is currently iterating over the URL history.
2094=Incremental Crawls
2095=Number of incremental crawls in progress.
2096=Filtering Documents
2097=The number of documents currently being filtered.
2098=Started Documents
2099=The number of documents initiated into the Gatherer service. This includes the number of documents on hold, in the active queue, and currently filtered. When this number goes to zero during a crawl, it means the crawl will be done soon.
2100=Retries
2101=The total number of times a document access has been retried. Having this number high may indicate a problem with accessing the data.
2102=Retries Rate
2103=The number of retries per second.
2110=Adaptive Crawl Errors
2111=Documents incorrectly rejected by adaptive crawl
2116=Changed Documents
2117=Documents which have changed since the last crawl
2118=Document Moves/Renames
2119=The number of Move/Rename notifications.
2120=Document Move and Rename Rate
2121=The number of document Moves and Renames per second.
2122=Unique Documents
2123=Number of unique documents in the system. Documents are considered not unique if their contents is the same.
2124=History Recovery Progress
2125=Percentage of the history recovery completed
2126=Search Gatherer
2127=Counters for the Windows Search Service Gathering service object
2128=Notification Sources
2129=Currently connected external notification sources.
2130=Ext. Notifications Received
2131=The total number of notifications received from all notification sources excluding file system.
2132=Ext. Notifications Rate
2133=The rate of external notifications received per second.
2134=Admin Clients
2135=The number of currently connected administrative clients.
2136=Heartbeats
2137=The total number of heartbeats counted since startup. A heartbeat occurs once every 10 seconds while the service is running. If the service is not running there will be no heartbeat and the number of ticks will not be incremented.
2138=Heartbeats Rate
2139=Displays one heartbeat every 10 seconds.
2140=Filtering Threads
2141=The total number of filtering threads in the system. This number is calculated based on your system resources.
2142=Idle Threads
2143=The number of threads waiting for documents.
2144=Document Entries
2145=The number of document entries currently in memory. Zero means no indexing activity is going on.
2146=Performance Level
2147=Indicates the level of the amount of system resources that the Gatherer service is allowed to use.
2148=Active Queue Length
2149=The number of documents waiting for robot threads. If this number is not 0, all threads should be filtering.
2150=Filter Processes
2151=The number of filtering processes in the system.
2152=Filter Processes Max
2153=The maximum number of filtering processes that have existed in the system since startup.
2154=Filter Process Created
2155=The total number of times a filter process was created or restarted. Having too many filter processes created indicates that filtering is having trouble with the data in the documents.
2156=Delayed Documents
2157=The number of documents delayed due to site hit frequency rules.
2158=Server Objects
2159=The number of servers recently accessed by the system.
2160=Server Objects Created
2161=The number of times a new server object had to be created.
2162=Filter Objects
2163=The number of filter objects in the system. Each filter object corresponds to a URL currently being filtered.
2164=Documents Filtered
2165=The number of times a filter object was created. This corresponds to the total number of documents filtered in the system since startup.
2166=Documents Filtered Rate
2167=The number of documents filtered per second.
2168=Time Outs
2169=The total number of timeouts detected by the system since startup.
2170=Servers Currently Unavailable
2171=A server becomes unavailable when a number of requests to that server time out.
2172=Servers Unavailable
2173=A server becomes unavailable when a number of requests to that server time out.
2174=Threads Accessing Network
2175=The number of threads waiting for a response from the filter process. If no activity is going on and this number is equal to number of filtering threads, it may indicate a network problem or unavailability of the server it is crawling.
2176=Threads In Plug-ins
2177=The number of threads waiting for plug-ins to complete an operation.
2178=Documents Successfully Filtered
2179=The number of documents successfully filtered.
2180=Documents Successfully Filtered Rate
2181=The number of successfully filtered documents per second.
2182=Documents Delayed Retry
2183=The number of documents that will be retried after time-out. When this is non-zero, it means that the local server it is crawling is shut down.
2184=Word Breakers Cached
2185=Number of available cached word breakers instances
2186=Stemmers Cached
2187=Number of available cached stemmer instances. Too many may indicate a resource usage problem.
2188=All Notifications Received
2189=The total number of notifications received from all notification sources including file system.
2190=Notifications Rate
2191=The rate of external notifications received per second.
2192=System IO traffic rate
2193=System IO (disk) traffic rate in KB/s detected by back off logic
2194=Reason to back off
2195=The code describing why the Gatherer service went into back off state. 0 - up and running 1 - high system IO traffic 2 - high notifications rate 3 - delayed recovery in progress (not implemented) 4 - back off due to user activity 5 - Battery Low 6 - Memory Low 99 - back off for some internal reason (forced by Search itself) While backing off, no indexing is performed. To resume the indexing you must eliminate the reason for back off. If the Gatherer service is in back off state, the Search service is paused and there is a message in the event log.
2196=Threads blocked due to back off
2197=The number of threads blocked due to back off event
2198=Search Indexer
2199=Indexer PlugIn statistics
2200=Master Index Level.
2201=The level of the master index.
2202=Master Merges to Date
2203=Number of Master Merges to Date
2204=Master Merge Progress
2205=Master Merge Progress
2206=Shadow Merge Levels
2207=Shadow Merge Levels
2208=Shadow Merge Levels Threshold
2209=Shadow Merge Levels Threshold
2210=Persistent Indexes
2211=Number of Persistent Indexes
2212=Index Size
2213=Size of Index
2214=Unique Keys
2215=Number of Unique Keys
2216=Documents Filtered
2217=Number of Documents Filtered
2218=Work Items Created
2219=Number of invalidator work items that were created
2220=Work Items Deleted
2221=Number of invalidator work items that were deleted
2222=Clean WidSets
2223=Number of clean WidSets
2224=Dirty WidSets
2225=Number of dirty WidSets
2226=Master Merges Now.
2227=Indicator if a master merge is going on.
2228=Active Connections
2229=Active Connections
2230=Queries
2231=Number of Queries
2232=Queries Failed
2233=Number of Queries Failed
2234=Queries Succeeded
2235=Number of Queries Succeeded
2236=L0 Indexes (Wordlists)
2237=The number of L0 Indexes (Wordlists)
2238=L0 Merges (flushes) Now.
2239=The number of L0 merges (flushes) in progress at any one moment.
2240=L0 Merge (Flush) Speed - Average
2241=The average value [documents/hour] computed for the speed of L0 merges (flushes) since the catalog has been loaded
2242=L0 Merge (Flush) - Count
2243=The number of L0 merges (flushes) since the catalog was loaded
2244=L0 Merge (Flush) Speed - Last
2245=The last value [documents/hour] computed for the speed of L0 merges (flushes).
2246=Persistent Indexes L1
2247=The number of L1 Indexes
2248=L1 Merges Now.
2249=The number of L1 merges in progress at any one moment.
2250=L1 Merge Speed - average
2251=The average value [documents/hour] computed for the speed of L1 merges since the catalog has been loaded
2252=L1 Merge - Count
2253=The number of L1 merges since the catalog was loaded
2254=L1 Merge Speed - last
2255=The last value [documents/hour] computed for the speed of L1 merges.
2256=Persistent Indexes L2
2257=The number of L2 Indexes
2258=L2 Merges Now.
2259=The number of L2 merges in progress at any one moment.
2260=L2 Merge Speed - average
2261=The average value [documents/hour] computed for the speed of L2 merges since the catalog has been loaded
2262=L2 Merge - Count
2263=The number of L2 merges since the catalog was loaded
2264=L2 Merge Speed - last
2265=The last value [documents/hour] computed for the speed of L2 merges.
2266=Persistent Indexes L3
2267=The number of L3 Indexes
2268=L3 Merges Now.
2269=The number of L3 merges in progress at any one moment.
2270=L3 Merge Speed - average
2271=The average value [documents/hour] computed for the speed of L3 merges since the catalog has been loaded
2272=L3 Merge - Count
2273=The number of L3 merges since the catalog was loaded
2274=L3 Merge Speed - last
2275=The last value [documents/hour] computed for the speed of L3 merges.
2276=Persistent Indexes L4
2277=The number of L4 Indexes
2278=L4 Merges Now.
2279=The number of L4 merges in progress at any one moment.
2280=L4 Merge Speed - average
2281=The average value [documents/hour] computed for the speed of L4 merges since the catalog has been loaded
2282=L4 Merge - Count
2283=The number of L4 merges since the catalog was loaded
2284=L4 Merge Speed - last
2285=The last value [documents/hour] computed for the speed of L4 merges.
2286=Persistent Indexes L5
2287=The number of L5 Indexes
2288=L5 Merges Now.
2289=The number of L5 merges in progress at any one moment.
2290=L5 Merge Speed - average
2291=The average value [documents/hour] computed for the speed of L5 merges since the catalog has been loaded
2292=L5 Merge - Count
2293=The number of L5 merges since the catalog was loaded
2294=L5 Merge Speed - last
2295=The last value [documents/hour] computed for the speed of L5 merges.
2296=Persistent Indexes L6
2297=The number of L6 Indexes
2298=L6 Merges Now.
2299=The number of L6 merges in progress at any one moment.
2300=L6 Merge Speed - average
2301=The average value [documents/hour] computed for the speed of L6 merges since the catalog has been loaded
2302=L6 Merge - Count
2303=The number of L6 merges since the catalog was loaded
2304=L6 Merge Speed - last
2305=The last value [documents/hour] computed for the speed of L6 merges.
2306=Persistent Indexes L7
2307=The number of L7 Indexes
2308=L7 Merges Now.
2309=The number of L7 merges in progress at any one moment.
2310=L7 Merge Speed - average
2311=The average value [documents/hour] computed for the speed of L7 merges since the catalog has been loaded
2312=L7 Merge - Count
2313=The number of L7 merges since the catalog was loaded
2314=L7 Merge Speed - last
2315=The last value [documents/hour] computed for the speed of L7 merges.
2316=Persistent Indexes L8
2317=The number of L8 Indexes
2318=L8 Merges Now.
2319=The number of L8 merges in progress at any one moment.
2320=L8 Merge Speed - average
2321=The average value [documents/hour] computed for the speed of L8 merges since the catalog has been loaded
2322=L8 Merge - Count
2323=The number of L8 merges since the catalog was loaded
2324=L8 Merge Speed - last
2325=The last value [documents/hour] computed for the speed of L8 merges.
5840=.NET CLR Networking
5841=&#1575;&#1604;&#1578;&#1593;&#1604;&#1610;&#1605;&#1575;​&#1578; &#1594;&#1610;&#1585; &#1605;&#1578;&#1608;&#1601;&#1585;&#1577;.
5842=Connections Established
Anonymous Coward (OP)
User ID: 77563213
Bulgaria
01/19/2020 01:03 AM
Report Abusive Post
Report Copyright Violation
Re: Why does everyone here hate Windows 10 so much?
it spies on you, it reboots and updates randomly, updates take hours even on lightning fast computers 1000000x as powerful as supercomputers from just 20 years ago, it looks ugly, buggy updates are often pushed and then retracted, i could go on

OpenBSD is the OS of the future, it's made to be secure but you have to be kind of an expert to even think about using it. Otherwise there's Debian.
 Quoting: Anonymous Coward 78301142


I have never once had a crash using it. Updates take a few minutes not hours with Ryzen 2nd gen Cpu. Maybe you PC is outdated, this could be the problem.

They likley just gather metadata not associated with you, its not spying.
 Quoting: Anonymous Coward 77563213


It sends in a screen capture every 30 seconds. This has been proven with DPI.
 Quoting: Anonymous Coward 46504284


it spies on you, it reboots and updates randomly, updates take hours even on lightning fast computers 1000000x as powerful as supercomputers from just 20 years ago, it looks ugly, buggy updates are often pushed and then retracted, i could go on

OpenBSD is the OS of the future, it's made to be secure but you have to be kind of an expert to even think about using it. Otherwise there's Debian.
 Quoting: Anonymous Coward 78301142


I have never once had a crash using it. Updates take a few minutes not hours with Ryzen 2nd gen Cpu. Maybe you PC is outdated, this could be the problem.

They likley just gather metadata not associated with you, its not spying.
 Quoting: Anonymous Coward 77563213


It sends in a screen capture every 30 seconds. This has been proven with DPI.
 Quoting: Anonymous Coward 46504284


bsflag





GLP