Update to Windows Performance Counter Event Errors

After installing all the performance counters that could be found for the services listed by lodctr /Q, a event viewer logged a couple of events associated with the performance counters.  This was used as an opportunity to run lodctr /R to check its affect on installed counters.  Some counter were lost. This is listed under Update 20190122 in LINK-> Performance Counter Event Errors

DoE, Great if Results aren't Qualitative and a Model Can Be Made

LINK-> (Using Design of Experiment Methods for Screening and Optimization of Quantitative Factors when Results are Qualitative) details the sequential use of traditional DOE (vertices generations and optimality selection) to generate a small set of trial experiments from the number of factors.  The best result from a set of experiments is used as the starting point for the next series of experiments.  It will eliminate unnecessary ones and optimize the others (screening and optimization) .  Its primary use is for situations when quantitative results are to difficult, impossible or time consuming to obtain or when a mathematical model of the system cannot be determined or it is not clear how to weight multiple responses.

Fixing Windows Performance Counter Event Errors

Windows performance counters can cause event errors like 1008, 1023, 2001 and 8317.  Information on fixing them is fragmented and the easily found reference information on using the Lodctr command to fix them is limited in depth. Link-> Performance Counter Event Errors discusses how Lodctr was used to resolve the events and items that may have caused others to have less success with the command.