MSFN Forum: Windows 7 unsolicited restoration of registry keys - MSFN Forum

Jump to content


Windows 7 forum rules

If you have questions about customizing Windows 7 that are vLite-specific, please post them in the vLite forum, not here. If you have questions regarding the unattended installation of Windows 7, please post them in the Unattended Windows 7/Server 2008 R2 section.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Windows 7 unsolicited restoration of registry keys By Windows modules installer, I guess

#1 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,274
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 14 July 2012 - 09:21 AM

I've mentioned this before, but now it really gets on my nerves and I want to know something more about it. It isn't system restore, it's happening every time Windows Modules Installer is started (for example, upon visiting Windows update and/or installing updates). Many registry keys that I've deleted previously, and (I suspect) some that should be gone forever through the way of removing components with WinToolkit, are restored, often with only empty keys and no values inside.

This is a very small sample of what gets restored (these are useless registry keys that I don't want to ever see in my registry):

Spoiler

The question is: where are the values stored? And the most important, is there a way to edit this list? Disabling fully the Windows Resource Protection (i guess this is a part of it) is out of question for me, because many things will stop to work (Windows Update, installing updates, possibly other things). And besides, I want to deal with the registry part only.

Thank you for any information on this.

GL


#2 User is offline   dencorso 

  • Adiuvat plus qui nihil obstat
  • Group: Super Moderator
  • Posts: 4,862
  • Joined: 07-April 07
  • OS:98SE
  • Country: Country Flag

Posted 15 July 2012 - 02:50 AM

I doubt this may be useful, but, just in case... KB815011 :unsure:

#3 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,274
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 15 July 2012 - 06:26 AM

View Postdencorso, on 15 July 2012 - 02:50 AM, said:

I doubt this may be useful, but, just in case... KB815011 :unsure:

Yeah, that's not it. It's about physical corruption, and this feature "repairs" when it sees something it doesn't like. :realmad:

GL

#4 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,274
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 15 July 2012 - 08:24 PM

I'm screwed. The information is inside manifests in WinSxS. (Most of) the listed values above belong to IE, so with every cumulative update they will get restored. Also other updates reinstall whatever they like.

Windows 7 really really really doesn't want you to walk astray from defaults. :realmad: :realmad: :realmad:


GL

#5 User is offline   Tripredacus 

  • K-Mart-ian Legend
  • Group: Super Moderator
  • Posts: 8,665
  • Joined: 28-April 06
  • OS:Server 2012
  • Country: Country Flag

Posted 16 July 2012 - 09:24 AM

Something you could test on a VM or other system... just an idea (probably not a good one). Is to delete the data in those keys, then change the permissions on them so that they cannot be written to. So as an example, you would still have an ".ai" class but with no data. But a situation may occur that locking those keys would cause an update to fail if it couldn't write the registry key.

#6 User is offline   GrofLuigi 

  • GroupPolicy Tattoo Artist
  • PipPipPipPipPipPip
  • Group: Members
  • Posts: 1,274
  • Joined: 21-April 05
  • OS:none specified
  • Country: Country Flag

Posted 16 July 2012 - 09:29 AM

View PostTripredacus, on 16 July 2012 - 09:24 AM, said:

Something you could test on a VM or other system... just an idea (probably not a good one). Is to delete the data in those keys, then change the permissions on them so that they cannot be written to. So as an example, you would still have an ".ai" class but with no data. But a situation may occur that locking those keys would cause an update to fail if it couldn't write the registry key.

That would be no different than current situation - they exist and they are empty. I made a .reg file to undo changes, but as far as I can see, all of the updates are different. For example, some restore tablet (ink) CLSIDs with empty keys. The bloat is unbelievable.

GL

#7 User is offline   jaclaz 

  • The Finder
  • Group: Developers
  • Posts: 11,420
  • Joined: 23-July 04
  • OS:none specified
  • Country: Country Flag

Posted 16 July 2012 - 10:12 AM

View PostGrofLuigi, on 16 July 2012 - 09:29 AM, said:

The bloat is unbelievable.

NO :no: .
Rest assured I can believe it :yes: . ;)

The amount of bloat is:
http://thesaurus.com...se/immeasurable

:angel

jaclaz

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy