Still not addressed is the permissions avoidance that accompanies this "update" and the additional fact that Microsoft has no information on this update... STILL. The first report I have seen of this problem was in March of 2010 and MS was supposed to have the article out in a "couple of days"... that hasn't happened yet
I spoke with a "tech" 2 days ago and today. He was clueless. After trying to brush me off without escalating the problem he finally conceded to escalation and I am supposed to be getting a call on April 18th 2011 about this issue from a "higher" office. probably just a buddy. He did call me back after giving me an initial callback date of 15 April 2011, but that was after I posted the results of our conversation on the microsoft website. I think the young man is watching my posts...
I spoke to Microsoft support today (a different office?... maybe in the same building) after the original tech and will be getting a call back from them. They have assigned me some type of case number, but this is also from an outsourced overseas call center, but I have patience persistence and a logical mind.
I posted this problem in CNET, but 2 responses just verify this is a mystery.
The only plausible info I have found so far is here http://forums.dpreview.com/forums/re...8&changemode=1
This refers to Norton sneaking drivers into Windows through this permissions-avoiding update. When I first talked to someone about this problem they asked if I had Norton installed on this PC, and I told them no.Edited by michael0156 - 4/14/11 at 1:28pm