how you think MS is gonna solve this problem? I believe that many ppl installed this update but have no clue to uninstall again because they do not get notified. If any problems arises when fixed files get deployed, there must be any way to ship around without being sent to desert later
Nah, not exactly hatred, she's accused me of posting a fake list, once win365 facts are out(it's just a matter of time), one final joke, and that's it, no point to waste time on a blogger.
Surely they will need to come up with some solution that does not require users to manually uninstall two previously bugged updates. Can't they do something like what they did with Update 1 - where the KB file was pushed again and again as changes were made (please excuse me if I have that process wrong)? At this point, I've pushed these updates to client and server machines at work (without issues, I might add). Hopefully the solution will not involve having to remove the already installed updates from those machines/systems.
A statement "fake list is fake" linking to my Neowin post with the MS guy's FB page, to be fair, that guy faced a certain job risk in posting that list. Anyway, what's the big deal? I saw many people flaming MJF for fake info's anyway, but of course, not so many as Thurrott.
When MS releases the fix, end users won't to uninstall anything. The update will just fix the underlying problems.
Im just winding you up, everyone related to Neowin and TWiT.tv report fake crap all the time, Neowin because they copy everyone else, and TWiT because they are all n00bs I stopped watching WW on TWiT when everything I posted that I learned from there was getting laughed at, and was complete BS
MS doesn't mention the companion file, but since the update takedown took them both down, there'd be no way to install it. It's probably a good idea to remove that one as well since it's taken down. That's a good question. There are also people that did a /resetbase on their system that won't be able to uninstall it. Hopefully they'll come up with a new update that will overwrite all the existing files regardless of the permanent status. Someone like abbodi1406 or Arseny92 would be better to explain something like that.
Paul may get this , but my first language is English, good has many means, just ask the good girl and bad girl . The development and breakthroughs here have always been good entertainment for sure. This is a gr8 place for OS info, just got some good info from Mr. Plissken . We all like a good party especially when all get along. respectfully yours
Well, Endgaget, TheVerge, WPCentral and others seems to take what MJFoley said seriously because they all wrote articles on this rumor.
murphy78, updates in GDR often are cumulative with the latest delta overwriting any previous version of the same component. However with that being said, and if the info from post 886617, 889939 and 877424 is taken into account also, this can easily get more complicated. It can be a bit of pain fixing any incorrect ACLs or unreferenced registry entries (even if normally the update component's manifests state operation=replace on all registry key values), when the applicability chain does not quite build up together, unless the latter update in question is crossversion and all discrepancies taken into account. We can only wait and see how MS goes to deal with this. Until then, there is no point to argue or speculate about.
Just another reason I've been recommending against using /resetbase unless people absolutely need the couple hundred megs of space.