Regedit.exe search crashing in W10 1511/TH2

Discussion in 'Windows 10' started by freevista, Nov 13, 2015.

  1. Deke40

    Deke40 MDL Novice

    Nov 17, 2015
    38
    1
    0
    Anybody had any luck with this problem with the new 10586.17?

    I'm still getting the failed search.
     
  2. rpo

    rpo MDL Expert

    Jan 3, 2010
    1,118
    917
    60
    10586.17 doesn't update regedit.exe. Version is still 10.0.10586.0.
     
  3. Deke40

    Deke40 MDL Novice

    Nov 17, 2015
    38
    1
    0
    Merci beaucoup.
     
  4. yomoma2

    yomoma2 MDL Senior Member

    Feb 27, 2010
    344
    111
    10
    #44 yomoma2, Dec 8, 2015
    Last edited: Dec 8, 2015
    Still no regedit fix on .29 also. On a system that was fine, after using many different usb pens it seems that new entries that make it crash were added. After replacing it with old regedit.exe 10240 the problem goes away.
     
  5. genenioo

    genenioo MDL Addicted

    Oct 9, 2007
    653
    113
    30
  6. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,585
    5,330
    210
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. freevista

    freevista MDL Member

    Jan 14, 2009
    100
    41
    10
    Version 10586.36, and still not fixed.
     
  8. WaltC

    WaltC MDL Addicted

    Mar 8, 2014
    518
    123
    30
    Make sure you aren't asking it to search a registry path...someone in another thread was doing that--when he only needed to search the last term in the string...crashed every time I tried it his way, xxxx\xxxx\xxxxx\xxxxxxx\xxxxxx\findme, but when I simply inserted the phrase I was trying to find, findme, it took me there instantly.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. SPDIF

    SPDIF MDL Junior Member

    Mar 30, 2014
    84
    38
    0
    Tested here at home in Windows 10 Enterprise version 10586.36, no hangs or anything with regedit whatsoever.

    it just do what it should do. Maybe the new update fixed this, i have no idea.

    The only thing i do different is that i started it from an elevated command prompt in windows.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. yomoma2

    yomoma2 MDL Senior Member

    Feb 27, 2010
    344
    111
    10
    On the affected machines, simply searching "findme" will hang after a while even under .36. Some external devices such as particular usb drives will cause the system to write these long registry entries that make the current regedit.exe crash, so a fresh system or one that never had those devices plugged won't have the same problem. Using old 10240 regedit.exe works fine on such systems, so unless they change the .exe, I don't believe we'll see a change to this.
     
  11. genenioo

    genenioo MDL Addicted

    Oct 9, 2007
    653
    113
    30
  12. yomoma2

    yomoma2 MDL Senior Member

    Feb 27, 2010
    344
    111
    10
    Since replacing it, I've never had to put it back again (there have been at least 3 or 4 CU's meanwhile). That's one of the first things I check, just to see if a newly updated file lands.
     
  13. genenioo

    genenioo MDL Addicted

    Oct 9, 2007
    653
    113
    30
    #53 genenioo, Dec 23, 2015
    Last edited: Dec 24, 2015
    Who knows? Maybe some day they'll fix it and that will be the end of this garbage.

    Update: I think I figured it out. When I run 'sfc /scannow' it puts back the original file.
     
  14. eta76

    eta76 MDL Novice

    Jul 19, 2016
    1
    0
    0
    There is an easy way to detect the location.

    1)
    Select the following item in te tree view:
    HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade

    Export this key and all its subkeys.

    2)
    Select the following item in te tree view again:
    HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade

    Press '*' on the numeric key pad, as this will expand all subitems of a treeview.
    RegEdit will start to expand all subitems, until it finds a problem:

    [Window Title]
    Error Opening Key

    [Content]
    {026e516e-b814-414b-83cd-856d6fef4822} cannot be opened.
    An error is preventing this key from being opened.

    [OK]


    Look for "{026e516e-b814-414b-83cd-856d6fef4822}" in the exported .reg file.
    Find this line.

    [HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Pnp\CurrentControlSet\Control\DeviceMigration\Devices\BTHENUM\{61118058-486C-4BB0-B4B8-ACE4DCADEC44}_LOCALMFG&0000\8&1EA02955&0&000000000000_00000000\Interfaces\{65e8773d-8f56-11d0-a3b9-00a0c9223196}#wave\Properties\{026e516e-b814-414b-83cd-856d6fef4822}]


    I think the problem of Regedit, is that is uses a 255 character buffer for the key name.
    And the name of these items are so long, for the keys and subkeys are nested pretty deep.

    I guess Bill was right 640 (kilo)byte should be enough for everyone :D
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    29,687
    46,043
    390
    With RS1 i don't have the search problem anymore.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...