The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Orphan entry in control panel

    Discussion in 'Windows OS and Software' started by 6730b, Jul 15, 2019.

  1. 6730b

    6730b Notebook Deity

    Reputations:
    1,290
    Messages:
    803
    Likes Received:
    1,744
    Trophy Points:
    156
    Hello, w8.1, got this CPAppletExe thing, seemingly a remnant after uninstalling Intel PROSet/Wireless Control Panel.

    Digged through disk and regedit and can't find any relating .cpl or other obvious entries. So basically out of ideas.

    Not important but would be nice to crack the mystery. Anyone got hints on how \ from where this is fed into control panel?
    Thanks
     

    Attached Files:

    • cp.PNG
      cp.PNG
      File size:
      14.3 KB
      Views:
      265
    6730b, Jul 15, 2019
    #1
  2. Spartan@HIDevolution

    Spartan@HIDevolution Company Representative

    Reputations:
    39,567
    Messages:
    23,559
    Likes Received:
    36,826
    Trophy Points:
    931
    https://www.winhelponline.com/xp/cpicon.htm
     
    Spartan@HIDevolution, Jul 15, 2019
    #2
    6730b likes this.
  3. 6730b

    6730b Notebook Deity

    Reputations:
    1,290
    Messages:
    803
    Likes Received:
    1,744
    Trophy Points:
    156
    Thanks for replying. The given page link is containing similar info (some outdated) to what I found earlier and used to try to pinpoint the source of the cp entry.

    With no sign of anything applying to this CPAppletExe, only thing as a candidate for suspicion was a namspace entry with 'no value set', so (after a backup) deleted the key to see what would happen, and (by luck more than knowledge) that fixed it.
     
    6730b, Jul 16, 2019
    #3
    Spartan@HIDevolution likes this.