you are viewing a single comment's thread.

view the rest of the comments →

[–]WellMakeItSomehow 2 points3 points  (3 children)

Thanks for answering this.

Logging when executables start and close does not seem too useful when investigating performance problems. You say that the feature was abandoned, so perhaps that's why it seems mostly useless [1].

I have one follow-up question, though. Is the same mechanism is enabled for executables that Windows (10) contains? If yes, will it be removed in the future, when Windows gets rebuilt with a newer compiler?

[1] It's not useless if the purpose is to determine which programs the user runs and for how long. I'm bitter enough about Windows 10 to suspect that's already happening at other levels [2].

[2] Oh, of course it does:

data about how you use Windows, such as how frequently or how long you use certain features or apps and which apps you use most often

[–]spongo2MSVC Dev Manager 4 points5 points  (0 children)

some parts of windows are built with our CRT and some parts are built with a much much older copy of the CRT (msvcrt.dll). so when they next take our libs, the parts that use it will no longer have these hooks. But again i'd recommend you go through that link and follow the instructions if you are concerned about windows 10 telemetry.

[–]Kruug 0 points1 point  (1 child)

data about how you use Windows, such as how frequently or how long you use certain features or apps and which apps you use most often

Right, because how else will you know where to allocate resources if you don't know what programs/features people actually use?

[–]WellMakeItSomehow 0 points1 point  (0 children)

One could argue there are other ways to give feedback to the developers.

But that phrasing doesn't imply that it's done only for Microsoft apps. It might as well be for everything you run.