%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%3CLINGO-SUB%20id%3D%22lingo-sub-1564152%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1564152%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20so%20finally%2C%20some%20feedback%20from%20Microsoft.%20The%20current%20%22culprit%22%20MIGHT%20be%20related%20to%20a%20non-removable%20update%20(KB4559309)%20that%20installs%20the%20new%20Chrome%20based%20Edge%20browser.%20However%2C%20I%20have%20my%20doubts%20that%20it%20is%20the%20ONLY%20cause.%20My%20desktop%20HAS%20the%202004%20updates%2C%20but%20does%20NOT%20have%20this%20update%2C%20and%20does%20NOT%20have%20the%20new%20Edge%2C%20but%20STILL%20has%20horrible%20performance%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20DID%20mitigate%20them%20for%20normal%20running%20mostly%2C%20by%20stopping%20and%20disabling%20the%20SYSMAIN%20and%20Windows%20Search%20services.%20However%2C%20I%20still%20have%20long%20reboot%2Frestart%20times%2C%20much%20longer%20then%20before%202004%20update.%26nbsp%3B%20I%20AM%20a%20user%20with%20MalwareBytes%20premium%20AV%2C%20that%20was%20supposed%20to%20be%20a%20factor%20in%20normal%20work%20going%20slow%2C%20but%20I%20have%20the%20later%20updates%20to%20it%20that%20stop%20that%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1586848%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1586848%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%3A%20I%20just%20found%20the%20original%20URL%20link%20for%20the%20very%20interesting%20(and%20long)%20article%20on%20the%20MS%20Answers%20forum%2C%20that%20was%20referenced%20in%20the%20PCGAMERS%20site%20where%20I%20got%20the%20info%20for%20my%20post%20above%2C%20regarding%20the%20very%20suspect%20update%20for%20deploying%20the%20new%20EDGE%20browser%20(KB4559309).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESome%20users%20are%20even%20saying%20that%20the%20update%20interfered%20with%20their%20manufacturers%20Motherboard%20Chipset%20drivers%2C%20and%20that%20they%20had%20to%20reinstall%20them%20to%20get%20back%20the%20previous%20performance.%20Others%20have%20NOT%20seen%20that%2C%20but%20are%20still%20stuck%20with%20bad%20performance.%20However%2C%20there%20are%20%3CSTRONG%3E22%20PAGES%20of%20complaints%3C%2FSTRONG%3E%20on%20this%20post%20alone.%20%3CSTRONG%3EThe%20fact%20the%20the%20errant%20update%20is%20NOT%20uninstallable%20makes%20the%20issue%20MUCH%20worse%20than%20it%20should%20otherwise%20be%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fwindows%2Fforum%2Fwindows_10-update%2Fupdate-kb4559309-makes-computer-unbearably-slow%2F31b8d053-8256-41b9-9c26-f9faaaa4e0ae%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fwindows%2Fforum%2Fwindows_10-update%2Fupdate-kb4559309-makes-computer-unbearably-slow%2F31b8d053-8256-41b9-9c26-f9faaaa4e0ae%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EHopefully%20now%20THIS%20above%20is%20seen%20on%20THIS%20Tech%20Community%2C%20maybe%20it%20will%20give%20more%20traction%20and%20viewings%2Fposting%20on%20BOTH.%20Users%20and%20tech%20folks%20need%20to%20speak%20up%20on%20this%2C%20and%20get%20it%20sorted%20out%2C%20as%20there%20are%20a%20LOT%20of%20fed%20up%20and%20angry%20users%20out%20there.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1591217%22%20slang%3D%22en-US%22%3ERe%3A%20Welcome%20Back%20AskPerf!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1591217%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F492777%22%20target%3D%22_blank%22%3E%40Perseous%3C%2FA%3EYou%20were%20asking%20how%20this%20works.%20Well%2C%20at%20this%20point%2C%20I%20am%20unsure%2C%20as%20it%20seems%20after%20the%20initial%20opening%20post%20by%26nbsp%3B%20%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%20there%20are%20no%20actual%20information%20posts%20FROM%20microsoft%2C%20and%20only%20my%20few%20posts%20about%20Performance%20Issues%20after%20users%20get%20the%20Windows%2010%202004%20update%2C%20and%20further%20issues%20after%20KB4559309.%20I%20would%20urge%20you%20and%20any%20other%20technical%20readers%20who%20have%20had%20experiences%20of%20these%20problems%2C%20to%20post%20them%20here%20AND%20on%20Feedback%20Hub%2C%20and%20hope%20that%3A%3C%2FP%3E%3CP%3E1)%20Craig%20will%20read%20them%20and%20pass%20them%20along%20to%20his%20colleagues%20to%20review%20and%20comment%3C%2FP%3E%3CP%3E2)%20The%20correct%20teams%20that%20(might%20be)%20looking%20at%20those%20issues%20from%20here%20or%20Feedback%20Hub%20will%20comment%20and%20provide%20feedback%20as%20to%20WHAT%2FWHEN%20Microsoft%20will%20be%20doing%20to%20mitigate%20the%20issues%20raised.%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

8 Comments
Occasional Visitor

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

Senior Member

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?

Senior Member

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.

Senior Member

OK, so finally, some feedback from Microsoft. The current "culprit" MIGHT be related to a non-removable update (KB4559309) that installs the new Chrome based Edge browser. However, I have my doubts that it is the ONLY cause. My desktop HAS the 2004 updates, but does NOT have this update, and does NOT have the new Edge, but STILL has horrible performance issues.

 

I DID mitigate them for normal running mostly, by stopping and disabling the SYSMAIN and Windows Search services. However, I still have long reboot/restart times, much longer then before 2004 update.  I AM a user with MalwareBytes premium AV, that was supposed to be a factor in normal work going slow, but I have the later updates to it that stop that issue.

Senior Member

FYI: I just found the original URL link for the very interesting (and long) article on the MS Answers forum, that was referenced in the PCGAMERS site where I got the info for my post above, regarding the very suspect update for deploying the new EDGE browser (KB4559309).

 

Some users are even saying that the update interfered with their manufacturers Motherboard Chipset drivers, and that they had to reinstall them to get back the previous performance. Others have NOT seen that, but are still stuck with bad performance. However, there are 22 PAGES of complaints on this post alone. The fact the the errant update is NOT uninstallable makes the issue MUCH worse than it should otherwise be:

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/update-kb4559309-makes-computer-...

Hopefully now THIS above is seen on THIS Tech Community, maybe it will give more traction and viewings/posting on BOTH. Users and tech folks need to speak up on this, and get it sorted out, as there are a LOT of fed up and angry users out there.

Senior Member

@PerseousYou were asking how this works. Well, at this point, I am unsure, as it seems after the initial opening post by  @CraigMarcho there are no actual information posts FROM microsoft, and only my few posts about Performance Issues after users get the Windows 10 2004 update, and further issues after KB4559309. I would urge you and any other technical readers who have had experiences of these problems, to post them here AND on Feedback Hub, and hope that:

1) Craig will read them and pass them along to his colleagues to review and comment

2) The correct teams that (might be) looking at those issues from here or Feedback Hub will comment and provide feedback as to WHAT/WHEN Microsoft will be doing to mitigate the issues raised.