%3CLINGO-SUB%20id%3D%22lingo-sub-386881%22%20slang%3D%22en-US%22%3EWelcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386881%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone!%20Welcome%20to%20the%20new%20home%20of%20the%20AskPerf%20blog.%20We%20have%20recently%20moved%2C%20and%20many%20things%20have%20changed%20in%20the%20years%20since%20the%20last%20post%20here.%20The%20owners%20of%20the%20blog%20have%20moved%20on%20to%20bigger%20and%20better%20things%2C%20so%20I%20have%20decided%20to%20bring%20it%20back%20to%20life%2C%20and%20bring%20some%20new%20fresh%20content%20to%20help%20the%20community.%20The%20Performance%20team%20has%20actually%20been%20split%20to%20two%20teams%20internally%20at%20Microsoft%2C%20one%20is%20still%20called%20%22Performance%22%20and%20the%20other%20is%20called%20%22User%20Experience%22%2C%20or%20UEX.%20Between%20the%20two%20teams%2C%20we%20will%20still%20provide%20information%20on%20all%20of%20the%20topics%20that%20we%20cover%2C%20here%20under%20one%20roof.%20So%20welcome%20back%2C%20and%20we%20will%20be%20providing%20some%20information%20here%20soon.%3CBR%20%2F%3E%3CBR%20%2F%3E-Craig%20Marcho%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-386881%22%20slang%3D%22en-US%22%3E%3CP%3EWelcome%20Back%20AskPerf!%20After%20some%20years%20of%20hibernation%2C%20we%20are%20bringing%20back%20the%20AskPerf%20blog!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-392987%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-392987%22%20slang%3D%22en-US%22%3E%3CP%3EYay!!%20Lets%20get%20it%20rolling.....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-391787%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-391787%22%20slang%3D%22en-US%22%3E%3CP%3EWaiting%20eagerly!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388419%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388419%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20up%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F301777%22%20target%3D%22_blank%22%3E%40CraigMarcho%3C%2FA%3E%26nbsp%3B!!%20Let's%20post%20some%20content!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072139%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072139%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20time%20posting%20on%20this%20and%20not%20sure%20how%20it%20works.%26nbsp%3B%20But%20I%20see%20that%20there%20have%20not%20been%20to%20many%20posts%20here.%26nbsp%3B%20How%20does%20this%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1507663%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507663%22%20slang%3D%22en-US%22%3E%3CP%3EOK%20here%20is%20a%20%22starter%20for%2010%22%3A%20How%20about%20an%20article%20on%20the%20performance%20issues%20causing%20some%20users%20grief%2C%20after%20having%20Feature%20Update%202004%20installed.%3C%2FP%3E%3CP%3EThere%20are%20many%20reports%20of%20this%20in%20the%20MS%20Answers%20forum%2C%20and%20Feedback%20contains%2050%2B%20items%20about%20FU2004%2Cmany%20with%20no%20comments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20impression%20I%20am%20getting%2C%20is%20that%20those%20with%20older%20devices%20with%20HDD%20see%20the%20performance%20issues%20(slow%20restart%2Freboot%2C%20slower%20internet%2C%20search%20indexer%20and%20sysmain%2Fprefretch%20hogging%2Fslowing%20the%20machines)%20much%20more%20noticeably%20than%20those%20with%20SSD%2C%20so%20it%20is%20just%20possible%20that%20the%20insider%20groups%2C%20and%20the%20main%20testing%20groups%20were%20not%20measuring%20performance%2C%20and%20not%20noticing%20it%20either%2C%20as%20they%20would%20most%20likely%20have%20later%2C%20well%20configured%20systems%20with%20SSD%2C%20to%20help%20with%20faster%20testing%20and%20deployment%20and%20validation%20for%20product%20readiness.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20as%20this%20appears%20to%20be%20the%20%22external%22%20public%20facing%20side%20of%20the%20%22Performance%20Team%22%2C%20rather%20than%20highlighting%20items%20that%20started%20life%20in%202015%2C%20how%20about%20getting%20more%20%22proactive%22%20stuff%20on%20here%2C%20where%20(hopefully)%2C%20your%20group%20can%20get%20feedback%20from%20the%20%22coal%20face%22%20internal%20teams%2C%20that%20are%20working%20on%20fixing%20Feature%20Update%202004%2C%20AND%20any%20other%20known%20issues%20with%20ANY%20of%20the%20Windows%20internal%20functional%20areas%20that%20are%20currently%20known%20to%20cause%20performance%20hits%20(especially%20post-2004%20update)%2C%20and%20what%20Microsoft%20is%20doing%20to%20help%20users%20get%20back%20to%20the%20performance%20and%20productivity%20they%20had%20before%20it%20got%20installed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20be%20aware%20that%20performance%20issues%20can%20be%20very%20frustrating%20for%20most%20normal%20users%2C%20who%20lack%20any%20diagnostic%20knowledge%20and%20tools%2C%20to%20find%20the%20real%20issues.%20It%20should%20be%20Microsoft%20teams%20like%20yours%2C%20who%20have%20access%20to%20the%20debug%20tools%20that%20the%20public%20does%20NOT%20have%2C%20to%20detect%20and%20iron%20out%20these%20things%20BEFORE%20big%20changes%20get%20into%20mainstream%20use%2C%20and%20this%20blog%20COULD%20be%20a%20good%20vehicle%20to%20convey%20Microsoft's%20current%20activities%20and%20action%20plans%20to%20reassure%20users%2C%20and%20help%20them%20move%20forward%20to%20the%20experience%20they%20are%20expecting%20from%20Windows%2010.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hello Everyone! Welcome to the new home of the AskPerf blog. We have recently moved, and many things have changed in the years since the last post here. The owners of the blog have moved on to bigger and better things, so I have decided to bring it back to life, and bring some new fresh content to help the community. The Performance team has actually been split to two teams internally at Microsoft, one is still called "Performance" and the other is called "User Experience", or UEX. Between the two teams, we will still provide information on all of the topics that we cover, here under one roof. So welcome back, and we will be providing some information here soon.

-Craig Marcho

5 Comments
Occasional Visitor

What up @CraigMarcho !! Let's post some content! :)

Regular Visitor

Waiting eagerly!

Occasional Visitor

Yay!! Lets get it rolling.....

Occasional Visitor

First time posting on this and not sure how it works.  But I see that there have not been to many posts here.  How does this work?

Frequent Visitor

OK here is a "starter for 10": How about an article on the performance issues causing some users grief, after having Feature Update 2004 installed.

There are many reports of this in the MS Answers forum, and Feedback contains 50+ items about FU2004,many with no comments.

 

The impression I am getting, is that those with older devices with HDD see the performance issues (slow restart/reboot, slower internet, search indexer and sysmain/prefretch hogging/slowing the machines) much more noticeably than those with SSD, so it is just possible that the insider groups, and the main testing groups were not measuring performance, and not noticing it either, as they would most likely have later, well configured systems with SSD, to help with faster testing and deployment and validation for product readiness.

 

So, as this appears to be the "external" public facing side of the "Performance Team", rather than highlighting items that started life in 2015, how about getting more "proactive" stuff on here, where (hopefully), your group can get feedback from the "coal face" internal teams, that are working on fixing Feature Update 2004, AND any other known issues with ANY of the Windows internal functional areas that are currently known to cause performance hits (especially post-2004 update), and what Microsoft is doing to help users get back to the performance and productivity they had before it got installed.

 

Please be aware that performance issues can be very frustrating for most normal users, who lack any diagnostic knowledge and tools, to find the real issues. It should be Microsoft teams like yours, who have access to the debug tools that the public does NOT have, to detect and iron out these things BEFORE big changes get into mainstream use, and this blog COULD be a good vehicle to convey Microsoft's current activities and action plans to reassure users, and help them move forward to the experience they are expecting from Windows 10.