Explorer.exe non-stop "RetailDemo" registry calls

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 1,853
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #11

    pepanee said:
    To Rick: Sorry, I just put 2 and 2 together, and saw you said you had your Service removed. So the picture you got was probably off the internet. So there's a bunch of text that I typed above that doesn't apply. Just ignore the stuff that doesn't apply. lol.
    AND
    I just read your edit above. I think I just confused myself or something. Haha. Don't worry about it,.
    That was my fault. It was an old screenshot from, I think, v1809. It was only when I checked that I realised Disk Clean-up has changed and the entry isn't in current Windows installs. With hindsight I should have deleted the screenshot rather than add the edit.

    These days I just use a PowerShell script to delete the service and cleanup. It has to be run as Administrator (and I compiled it for ease of use and to make it silent):
    Code:
    # Delete the RetailDemo service
    sc.exe delete "RetailDemo"
    
    # Delete RetailDemo files
    Get-ChildItem -Path C:\ -Recurse -Force -Confirm:$false | Where{$_.Name -Match "RetailDemo"} | Remove-Item -recurse -force -Confirm:$false
    Explorer.exe non-stop "RetailDemo" registry calls-del_retaildemo_service.png

    I use sc.exe for convenience. It's just easier than:
    Code:
    Stop-Service 'RetailDemo'; Get-CimInstance -ClassName Win32_Service -Filter "Name='RetailDemo'" | Remove-CimInstance
    ... and I'm using Windows PowerShell v5.1 so can't use the Remove-Service cmdlet.

    Hope this helps...
      My Computer


  2. Posts : 2,984
    Windows 10 Pro for the Bro
       #12

    Cool little script / shortcuts. I'm sure other people who come across this with wanting to limit their Services / etc would be glad they came across the ideology of eliminating useless Services and stuff.

    But of course, we do NOT recommend the original poster deleting this Service. Please do not delete this Service; only disable it using the instructions from the suggestions above, to see if it fixes the consistent commands that the computer keeps sending to the Registry.
      My Computer


  3. Posts : 5
    tetrasect
    Thread Starter
       #13

    pepanee said:
    RickC is right. Why is your computer always resetting that option constantly? (Techniocally speaking, n othing bad is happening over time, but something is making your computer to sconsistently wanting to always set the default values for that. Kinda weird.

    What does this show?
    Attachment 389913
    Is yours Manual?
    If not, set it to Manual. Restart the computer. Watch Process Monitor. Did it stop logging all that? Problem Solved.
    If still logged, See if you can Disable this service, and restart the computer. Now watch Process Monitor. Did it stop? Problem Solved.
    If not, comment back...
    The service is set to disabled...

    - - - Updated - - -

    RickC said:
    I'm using the same Windows 22H2 19045.2846 version and I don't see those constant RetailDemo open/set/close key operations in Process Monitor so I think there IS an issue... but I don't know why Explorer is doing what it's doing.

    Perhaps more detail?

    Q. What made you look using ProcMon?
    Q. Have you filtered out any FAILURE or NAME NOT FOUND events from the ProcMon results?
    Q. What value is the RegSetInfoKey operation writing?
    Q. How long since this started?
    Q. Is this a new/very recent install of Windows?

    The reason I ask is that, following completion of OOBE, Windows should have removed all Retail Demo Experience components within 7 days (unless your device has 32GB or less of storage, in which case the interval before removal is only half-an-hour).

    As a result, Windows shouldn't really have any reason to be worrying about Retail Demo. So, if Explorer is writing a value and querying another value within a RetailDemo registry branch then that suggests something is wrong - perhaps an OOBE glitch or maybe it's because it's a very recent/new install and the cleanup interval has not yet been reached.

    Hope this helps...
    Thanks for the help.

    Q. What made you look using ProcMon?

    My mechanical HDD keeps spinning up and I was trying to find out what the cause was. I excluded the networking and some other apps that I have running in the background to try clean up the interface and that's when I noticed Explorer.exe doing this registry call thing, basically filling up the log all on it's own.

    Q. Have you filtered out any FAILURE or NAME NOT FOUND events from the ProcMon results?

    I have NAME NOT FOUND HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Feeds\DSB\GleamSizeEnum popping up every now and again, not very frequently. Not sure if that was there the other day.

    There's also NAME NOT FOUND HKCU\Software\Classes\CLSID\{c2f03a33-21f5-47fa-b4bb-156362a2f239} and NAME NOT FOUND HKCU\Software\Classes\CLSID\{c2f03a33-21f5-47fa-b4bb-156362a2f239}\InprocServer32.

    Q. What value is the RegSetInfoKey operation writing?

    Double-clicking on the event gives me this info:

    KeySetInformationClass: KeySetHandleTagsInformation
    Length: 0

    Q. How long since this started?
    Q. Is this a new/very recent install of Windows?

    Yeah I did an in-place upgrade from win7 to win10 last weekend. It's been 7 days already though...
      My Computer


  4. Posts : 1,853
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #14

    Thanks for the answers to my questions.

    If you carried out the in-place upgrade last weekend then it hasn't actually been 7 days since.

    Perhaps post back after next Monday?

    If the behaviour hasn't stopped by then, I would suggest a clean install. I know... a pain, but, IMO, it's almost impossible to work out what's happening otherwise. Your choice.
      My Computer


  5. Posts : 2,984
    Windows 10 Pro for the Bro
       #15

    Try setting the service to Manual, like in my photo. Restart the computer.

    Monitor to see if that continues or not..
      My Computer


  6. Posts : 1,853
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #16

    pepanee said:
    Try setting the service to Manual, like in my photo. Restart the computer.

    Monitor to see if that continues or not..
    With respect, the RetailDemo service is supposed to set itself to manual after 7 days post-OOBE (or after 30 mins if the device has 32GB storage space or less) anyway. See here for more details.

    So, if the OP sets the service manually to 'Manual' then there's no indication whether Windows' post-OOBE processes have worked properly, including any automatic changes to the built-in Retail Demo Experience if it's not triggered.

    IMO it's fine to change the service status... but not within the post-OOBE qualifying period if you want to check what's happening.

    I suggest the OP just waits for another day or two (i.e. 7 days or more, post-OOBE) and sees whether the issue settles down automatically.
      My Computer


  7. Posts : 2,984
    Windows 10 Pro for the Bro
       #17

    Okay that sounds good; You're right RickC.
    Your post makes more sense than my "try this out" kind of method. We'll see what his computer says after that certain amount of days. Let's hope the issue resolves itself after that time period.
      My Computer


  8. Posts : 840
    Windows 7
       #18

    The scheduled task for RetailDemo cleanup is set to block Run on demand. But you can change the setting in Task Scheduler, and then run it manually. Evidently they don't want you playing with the script.
      My Computer


  9. Posts : 1,680
    X
       #19

    Windows accesses the registry a hundred times a second ... even when you're "not doing anything" with the computer.
    So I wouldn't raise an eyebrow over Windows doing so with respect to this retail demo thing.
      My Computer


  10. Posts : 1
    Win 10 LTSC
       #20

    Hello!

    I had the same issue and it annoyed me. I found out (in my case) that it was caused by the "f.lux" software !
    Once i close f.lux the requests stop.

    When i open f.lux (to change color temperature or some settings) i makes even more of thoses same requests, the process monitor is flooded.

    edit : going to the f.lux forum, i found this : f.lux triggers repeated explorer registry access on v4.130 (f.lux forum)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:02.
Find Us




Windows 10 Forums