Export registry values

Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA

--
remove fred before emailing

"scbs29" wrote in message
...
Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA


Seek and ye shall find :-)
http://lmgtfy.com/?q=find+and+export+registry+keys

The first listing is one that I've used a few times:
http://www.nirsoft.net/utils/regscanner.html
--
SC Tom

scbs29 wrote:
Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA


Have a need to import those GWX values later ?
If so, for what purpose ?



--
...winston
msft mvp consumer apps

.. . .winston wrote:
scbs29 wrote:
Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA


Have a need to import those GWX values later ?
If so, for what purpose ?

He is obviously on the war path to remove
the "Upgrade to Windows 10" nag. As you know
what the GWX series of files is for - they're
the ones delivered by the '583 patch.

Paul

Paul wrote:
. . .winston wrote:
scbs29 wrote:
Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA


Have a need to import those GWX values later ?
If so, for what purpose ?

He is obviously on the war path to remove
the "Upgrade to Windows 10" nag. As you know
what the GWX series of files is for - they're
the ones delivered by the '583 patch.

Paul


I know full well what GWX is, I was curious if the purpose of the export
was to provide the option to import later.

If removal, without import, is the objective...exporting holds less value.

--
...winston
msft mvp consumer apps

"scbs29" wrote in message
...
Hello all
Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA

Using RegScanner, I found 168 keys containing GWX. Not sure if I'd want to
delete that many keys without having a current disk image :-)
The OS may not be affected, but if it is, will it be able to boot well
enough to import those keys back in? Good question, but not one I'm willing
to test. If you do, let us know how it goes.
--
SC Tom

"SC Tom" wrote in message ...

"scbs29" wrote:

Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA

Using RegScanner, I found 168 keys containing GWX. Not sure if I'd want to
delete that many keys without having a current disk image :-)
The OS may not be affected, but if it is, will it be able to boot well
enough to import those keys back in? Good question, but not one I'm
willing to test. If you do, let us know how it goes.

If you can't boot the system, try a safe boot and import your exported file
from there.

If a safe boot fails and you have a copy of the original Microsoft install
disk, boot it and let it come to its first stop asking you to do something.
Press SHIFT+F10 to open a command window; from that window you can run
Regedit. Load the appropriate hive(s) from the failed system into Regedit,
then (after editing the export file to change the keys to use the names
under which you loaded the hives) import the saved .REG file.

The hives can be found in drive:Windows\System32\Config - but note that
there are several hives that together represent HKLM. I suggest assigning
mnemonic names when importing the hives, such as 00-sys and 00-sw when
loading the SYSTEM and SOFTWARE hives respectively; the 00 at the front
keeps them at the top of the HKEY_LOCAL_SYSTEM tree in REGEDIT, and "sys"
and "sw" are easy mnemonics to remember. Using this scheme you would have
to edit (A COPY OF!!!) your exported Registry file to change

HKLM\SOFTWARE\Microsoft\Foobar
to
HKLM\00-sw\Microsoft\Foobar

When the hive is unloaded the updated file is written back to disk, and when
you boot the normal system that hive becomes the tree structure under
HKLM\SOFTWARE .

ObWarning: manipulating the Registry is always dangerous, and doing it from
an external system is even more so; you're doing heavy maintenance on a
locomotive while it's making an express run through hostile territory in the
middle of a tornado, and there's no "OOPS!" button. Use the suggested
procedure at your own risk.

Joe

On 6/25/2015 6:43 PM, Joe Morris wrote:
"SC Tom" wrote in message ...

"scbs29" wrote:

Is it possible to export all registry entries that contain a string,
eg. GWX.
I have looked in the registry and there are keys etc such as:
(C74C5910-D594-43DD-850F-3AFFEB98756D)
(Default) REG_SZ GWX
InProcServer32
(DEfault) REG_EXPAND_SZ
c:\Windows\System32\GWX\GWXUI.dll
TIA

Using RegScanner, I found 168 keys containing GWX. Not sure if I'd want to
delete that many keys without having a current disk image :-)
The OS may not be affected, but if it is, will it be able to boot well
enough to import those keys back in? Good question, but not one I'm
willing to test. If you do, let us know how it goes.

If you can't boot the system, try a safe boot and import your exported file
from there.

If a safe boot fails and you have a copy of the original Microsoft install
disk, boot it and let it come to its first stop asking you to do something.
Press SHIFT+F10 to open a command window; from that window you can run
Regedit. Load the appropriate hive(s) from the failed system into Regedit,
then (after editing the export file to change the keys to use the names
under which you loaded the hives) import the saved .REG file.

The hives can be found in drive:Windows\System32\Config - but note that
there are several hives that together represent HKLM. I suggest assigning
mnemonic names when importing the hives, such as 00-sys and 00-sw when
loading the SYSTEM and SOFTWARE hives respectively; the 00 at the front
keeps them at the top of the HKEY_LOCAL_SYSTEM tree in REGEDIT, and "sys"
and "sw" are easy mnemonics to remember. Using this scheme you would have
to edit (A COPY OF!!!) your exported Registry file to change

HKLM\SOFTWARE\Microsoft\Foobar
to
HKLM\00-sw\Microsoft\Foobar

When the hive is unloaded the updated file is written back to disk, and when
you boot the normal system that hive becomes the tree structure under
HKLM\SOFTWARE .

ObWarning: manipulating the Registry is always dangerous, and doing it from
an external system is even more so; you're doing heavy maintenance on a
locomotive while it's making an express run through hostile territory in the
middle of a tornado, and there's no "OOPS!" button. Use the suggested
procedure at your own risk.

Joe



I suggest you do a backup first with free ERUNT (Googe for it)

On 26/06/2015 02:41, Zaidy036 wrote:



I suggest you do a backup first with free ERUNT (Googe for it)


What!! are you saying to backup before exporting registry entries? Do
you know the major difference between "export" and "backup"?

Good Guy wrote:
On 26/06/2015 02:41, Zaidy036 wrote:



I suggest you do a backup first with free ERUNT (Googe for it)


What!! are you saying to backup before exporting registry entries? Do
you know the major difference between "export" and "backup"?



Think more proactive..it seems obvious the obvious the reason for export
of the GWX keys to subsequently remove them..thus making a backup before
or after exporting would still be appropriate. The system backup before
or after exporting but prior to deleting would be common except for the
exported file.

--
...winston
msft mvp consumer apps

| Using RegScanner, I found 168 keys containing GWX. Not sure if I'd want to
| delete that many keys without having a current disk image :-)

That program looks interesting. Thanks for posting it.
Search in Regedit is so bad...

The number of values isn't so important as
what they are. If they're under the \Software\
keys they're likely to just be various trivial settings.
Under HKCR\CLSID will be COM classes. Remove
one of those and you remove some kind of
functionality. On the other hand, if that functionality
is just part of ImposeWin10OnThisSucker.dll then it's
no big loss. If you do an export you may be able
to assess whether any of the values you're looking
at is critical.

Registry values proliferate quickly. Just a single
COM library could install dozens of values under
HKCR, HKCR\CLSID and HKCR\Typelib. If the update
had, say, 2 or 3 COM libraries used to maintain the
nags and handle Win10 downloads that could account
for 168 settings right there.

This all may have already been done by someone
else, too. I imagine a lot of people are trying to figure
out how to cleanly eliminate the nags.

A third possibility: I don't know how the update is
installed, but you may be able to figure out the reverse
steps from that. Many EXE updates are just SFX CAB
files. Once converted you get a CAB file full of system
files and maybe an INF file that runs the install.
Similarly, updates packaged as MSI files can be
unpacked and documented.