No worries Andre.
For xperf stuff we have two team blogs where you might be able to get some help.
AskPerf (blogs.technet.com/.../askperf) is our internal performance support team
NtDebugging (blogs.msdn.com/.../ntdebugging) is our internal debug team which regularly uses the tool.
As for the SSU update, I'm not 100% sure personally so I am going to find out now. I will post more once I have information.
--Joseph
Any news about the servicing stack update?
People are getting paranoid about it:
www.techarp.com/showarticle.aspx
André
Looks like the KB is published now: support.microsoft.com/.../976902
Looks like it was just an SSU update that was pushed out.
hi Joseph,
I saw the KB article, too. This is the corresponding SSu update for Sp1 RC. So, WindowsUpdate error which offered the update to all, not those who applied the registry setting?
Btw, I have an idea for a topic. Diagnostic Installing issues with reading the CBS.log and replacing damaged files from the DVD, like I did here:
social.technet.microsoft.com/.../ba7def75-8a18-407f-879f-8e0efb291458
I have the idea that the checkSUR tool can be made online. Is it possible to download the required files from the Internet (like the symbol servers when you need Debug symbols) and not putting them into the CAB files and releasing the update again ever 2nd month?
Can you also tell the MSFT employees to look in to the Sp1 technet forums? I'm doing my best to solve the Sp1 issues, but I can't diagnostic all things like bfsvc.exe (process exit code 21) and netcfg.exe failures.
André
Andre;
I'm not sure about the SSU, I just know it went out as an update.
Sure, I can work on something around replacing files from DVD. As for the CheckSUR piece, I like the idea but I think there might be some other ramifications of doing that, let me bat it around internally a little and see what people think.
Lastly, for the SP1 forums, I will send out mail to me team today and see if anyone can help out. No promises other than I will ask :)
.
Hi Joseph,
can you look at this topic, please (I see that you visited the Sp1 forum)?
social.technet.microsoft.com/.../eae0a67c-62c6-4d8e-9f3f-70623efa1c9a
it also shows the need of having the internet based checkSUR version.
I also had an user with a log where a file from the email junk filter update for Vista was broken. The bad thing is that this version was released months ago and you can't get it to extract the files.
Btw, I have a request for a new topic. Can you please explain, why mouting images with DISM from Windows 7 takes so long compared to Vista when using ImageX from Vista WAIK? What is different in DISM (Mount driver in WIndows 7 WAIK)?
And 1 thing, the update support.microsoft.com/.../2345886 often fails (netcfg fails). What to do there to fix this issues?
André
Perhaps a 'sticky' type post that outlines all the common servicing problems with links to the appropriate troubleshooting pages in this blog, or on microsoft.com.
Perhaps something on Windows Update and its interaction with the servicing stack. Related troubleshooting. An outline of the \Windows\SoftwareDistribution folder structure.
I like this idea Drew, I'll see what I can come up with in the coming weeks and post something as SP1 volume trails off.
@Andre "can you add better error message to WUSA.exe? "Doesn't apply to your PC" is the worst message ever. The question is why doesn't it apply."
Off topic but hopefully interesting ... this reminds me of Togs "Grey Doubt" bug: www.asktog.com/.../10MostWantedDesignBugs.html @Mysteriously dimmed menu items
Bug: Designers offer no way for users to discover why a given menu or option has been dimmed (grayed out), nor how to turn it back on.
Class of error: Users are teased with options that they cannot access without guessing what was in the designer's mind.
Proposed Fix: Make grayed-out objects clickable, revealing what has caused the object to be dimmed and what the user can do about it.
@joscon
you posted that you work on servicing tools for Windows 8.
The expand issue with the date/time is now fixed. Also installing updates with pkgmgr now uses the correct date/time values :) But 1 thing still occurs. If I use expand, the digital signature is not added to the extracted file. So I can't use expand to get a clean file to repair a corrupt file in WinSxS folder.
But the ugly error message "The update is not applicable to your computer" still doesn't say WHY.
I get this when I tried to run the x64 MSU on a x86 Windows 8 VM. Add a better error message in the Windows 8 Beta.
![joscon [Microsoft]](http://i1.social.s-msft.com/profile/u/avatar.jpg?displayname=joscon+%5bmicrosoft%5d&size=large){kind=avatar}
