Registry key

Discussion in 'Windows Server' started by Thomas Dubreuil, Nov 16, 2018.

  1. Thomas Dubreuil

    Thomas Dubreuil MDL Member

    Aug 29, 2017
    111
    157
    10
    #1 Thomas Dubreuil, Nov 16, 2018
    Last edited: Nov 17, 2018
    Can someone kindly export/share this registry key ?
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_en-us_
    for the problem I reported here

    It seems if I change winners default value to 10.0.17763.107 (instead of 10.0.17763.1) I don't get "corrupted" file repaired anymore.

    ps: I know it's false positive that can be safely ignored (and that sfc scannow is "overrated"), but I like to have it "clean" if possible. :)
     
  2. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,644
    2,297
    90
    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_en-us_9c6f7f32a5c78ebf]
    @="10.0"
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-p..inscripts.resources_31bf3856ad364e35_en-us_9c6f7f32a5c78ebf\10.0]
    "10.0.17763.1"=hex:01
    @="10.0.17763.1"
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Thomas Dubreuil

    Thomas Dubreuil MDL Member

    Aug 29, 2017
    111
    157
    10
    Thanks a lot!
    ok, had it like that originally...but only way to get out of the "sfc scannow loop" is to add "10.0.17763.107"=hex:01, and put @="10.0.17763.107" as default.
    I need to understand how the repair mecanism is done.
    Still looking for an "official" fix.