[20H2 19042.906] dfrgui.exe doesn't launch, unresponsive

After 19FEB2021 (the last Defrag event in the log), I found that the Defragment and Optimize Drives program no longer launches/functions on my machine. I also had been trying to open the "dfrgui.exe" within the System32 folder still to have it not open, nor create and processes within the Task Manager. Each time I try to open it, the cursor changes to the loading circle for only half a second before changing to the normal cursor again.

I have ran the System File Checker, DISM, and CHKDSK, to no avail. I even tried taking ownership of, and deleting/renaming any system files that had to do with Defrag and had SFC restore them multiple times, which was a success but the dfrgui.exe continued to be unresponsive.

Today I ran Defrag.exe from the Administrative Command Processor only to find that even Defrag.exe does nothing when the command is ran on any drive connected to the PC.
Even with the "/V" verbose command, nothing is done, no new Defrag events created in the Event Log, no disk activity, nothing at all.


Could there be something I am missing? I have tried everything I can think of, along with running extensive anti-malware, anti-virus, and anti-rootkit scans, all of which came back clean. My SSD and HDD are both in good health according to the S.M.A.R.T. data and performance ratings.

System Info:
Windows 10 Pro version 20H2 build 19042.906 64bit
1TB SAMSUNG NVMe M.2 SSD
1TB SeaGate Barracuda 7200rpm SATA HDD

topgundcp said:

I am running the same version and mine works fine. I normally have the schedule off and manually running it to optimize/defrag all at once using this .bat run as Admin.
From your screen shot I can't tell if you run it from the Admin Command Prompt or not.

Code:

@echo off
setlocal
cd /d %~dp0
net session >nul 2>&1
if %errorLevel% neq 0 echo Run As Admin !!! && pause && exit
set list=
setlocal EnableDelayedExpansion
set cmd="wmic logicaldisk get caption,drivetype,volumename | find /i ":""
for /f "tokens=1,2,3" %%A in ('!cmd!') do if %%B == 3 set list= !list! %%A
C:\Windows\System32\Defrag %list% /O /MultiThread & C:\Windows\System32\dfrgui.exe
 exit
rem Pause

Thank you for your response. Unfortunately your batch script didn't work. The command processor simply closes immediately after running the *.bat as Administrator. I edited the script a bit by turning echo on, and removing the exit command to see if there was any hidden error messages, or faults when ran within the Administrative Command Processor, and it seems all commands get executed correctly, yet there still is no result. See here:


There was also no log within the Event Viewer. I ran this script a variety of ways to ensure it was being executed correctly. I ran it within an existing Administrator Command Prompt window, I launched the *.bat as Administrator in a new process, I also even copied each command one by one and input them into the Admin Command Prompt... still, nothing, not even registerable activity on the HDD (D:), and just normal slight reading from the SSD (C:) of about 200~500kiloByte/s due to a background process being active.

topgundcp said:

Well, that is the same script that I use every day. It should not close until all SSD/HDD are optimized/drefraged. The Exit commnand will not run until dfrGUI.exe is closed.

I re-copied your batch script and made a new file. Then I proceeded to run this in Safe Mode with Command Prompt, and Safe Mode with Networking, however there was still no success. I also tried opening the "dfrgui.exe" in those modes as well, and it did nothing. I am not sure why my computer will not open the dfrgui.exe at all, it returns absolutely no errors or logs. It simply acts as if it doesn't know how to open. I proceeded to re-run "sfc /scannow" and it claims there's no corruption.

I also closely examined the Local Group Policy Editor and found absolutely nothing pertaining to the Defragmenter. HP's Support Assistant has a shortcut link for the dfrgui.exe but it also doesn't do anything. Perhaps my computer is just not compatible with that program any longer. Prior to this incident, I would run it manually every other week/twice a month, and had the Scheduled Optimization turned off. Looking around online, I found something that said perhaps the service was simply disabled, but upon opening the Services Applet, there is no services pertaining to Defrag, Defragmenter, Optimizing, ect on my system.

Initially, I ran these commands, in this order:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
[restarted computer]
sfc /scannow
[restarted computer]
sfc /scannow
[restarted computer]
chkdsk /r C:
[restarted computer, and allowed scan to complete]
sfc /scannow
[restarted computer one more time]
attempted to launch dfrgui.exe, no success.

Yes, I have installed the 2021-03 Cumulative Update Preview for Windows 10 Version 20H2 for x64-based Systems (KB5000842) on 30 MAR 2021.

I ran the command you stated above

Code:

dism /online /cleanup-image /restorehealth&sfc /scannow&pause

...and this was the result:

I restarted, with no improvement unfortunately.

- - - Updated - - -

After running one last command I could think of off the top of my head, it has solved my inability to open the dfrGUI.exe.

The command I used to solve this issue was

Code:

for %1 in (*.dll) do regsvr32 /s %1

this command is to re-register all system *.dll files, something I would've imagined that System File Checker would've done. It seems "defragsvc.dll" was the issue, as the service was missing from my service list as well, therefore it couldn't start the main GUI. After re-registering the file, the service was restored within the Services Applet (MSC), not even a reboot was required afterwards.

I really appreciate your time you have taken today to try and help, and your patience with my responses today @topgundcp , your *.bat script is also working as intended which is great!


I shall be a mystery about what had caused that *.dll file in question to cease working, and I will investigate my logs to try and find out if any program/system update installs on and/or after that date happened to mess with the file itself and/or it's registration information unintentionally, and silently.