Your reply was interesting due to a few things I have found altered applying the new iTunes update - 10.6.1.7. like album art work missing, double entries for every song in my library. Still investigating, but it appears a few settings in Sync in itunes have also been altered back to default and not picked up on the install as they were originally set to. I am beginning to think that the updates are stand alone packages scripted to update, but it is basically the same package whether you are a new user or an existing user. If this is the case, it would explain an aweful lot of the problems being experienced right across the board. Basically, the device and itunes settings files are not being cached on the installations, hence everything reverts to default. For those experiencing wireless and browser issues, this could be key to the problem.
I have a few days off on holiday, I will try and contact Apple's Software department and see if I can gain an insight into just what is going on. In the meantime the best advice I could offer anyone is to back up everything before updating, then reapply the backup after update - this will transfer all settings back to the ipad - which is obviously fine for the iOS updates. The same cannot be said for PC/Mac updating
In addition the Support pages for ipad on backup, indicate that media files in libraries are not backed up, only content on the iPad, if this is the case and settings in iTunes are not in a consistent state before and after updating, then various problems will then occur, dependent on iTunes settings and sync information in the database files on PC/Mac and idevice
If this is the case, it would present a significant bug in the way Updates talk to the Computer system prior to any operation.
I am somewhat intrigued by the whole process. I am also aware that there is still a bug in the updates in relation to recognising PC folder permissions, and those running updates in User accounts with elevation prompts due to UAC - User Access Control - may still find the elevation does not give them sufficient priveleges.
I have long suspected due to the wide range of problems across all levels of the programme and the devices on update, that a command permission or permissions must be less than what they need to be, that is they are not being given the right to impersonate on elevation, a key factor required on any modern computer, be it Mac or Windows system. My theory is that request for elevation have not been written into the software sufficiently robustly.
If I can get a copy of Xcode and IDE interface to run he COCOA code I might be able to track down the problem and suggest a patch.
Thankyou for your reply, happy that you were able to fix your own problems. Best wishes. Ct