Add or Remove Scan with Microsoft Defender Context Menu in Windows 10  

Ztruker said:

I have it turned on as that's thje way I prefer MBAM and Defender to run.

I'll turn it off and see what happens.

Thanks Shawn

Yup, that is the fix but I prefer it to run the other way so I'll turn it off if I need to scan individual files or folders.

Hmmm. The .reg file does not work for me.

Right-click on a file still does NOT show Windows Defender as an option

Win 10 Pro 64-bit v 21H1.

Had it for a while and would like to have it back. Don't know when it disappeared,

EDIT - Brink's post just a few up from here did the trick - turning off the switch in Malwarebytes! Win Def is back in right-click. I would NEVER have found that. Thanks, Brink !!!!!! (MalwareBytes Free gave me its promo of active protection for 14 days, and that had the switch Brinks shows four above.)

Hello @OldGrantonian,

I have just checked the REG Entries in the Tutorial for you against mine, and mine are exactly the same except for . . .

Tutorial Code

Code:

[HKEY_CLASSES_ROOT\CLSID\{09A47860-11B0-4DA5-AFA5-26D86198A780}\InprocServer32]
@="C:\\Program Files\\Windows Defender\\shellext.dll"

My Registry Entry

Code:

HKEY_CLASSES_ROOT\CLSID\{09A47860-11B0-4DA5-AFA5-26D86198A780}\InprocServer32
@="C:\Program Files\Windows Defender\shellext.dll"

I only have single \ separators instead of double \\ separators. I do NOT know if that will work for you.

@Brink will be able to clarify the correct REG Entries later.

I hope this helps.

Thanks for trying to help. That did not add anything to the context menu.

Paul Black said:

I only have single \ separators instead of double \\ separators.

It looks as if the double slashes are simply escapes.

I ran Shawn's reg first, without examining the results in the registry. I then ran your reg, and looked in registry. Only single backslashes were present.

Because your reg changed nothing in the registry (still single backslashes), I thought I might as well re-run Shaw's version to restore the registry to what it would have been if I hadn't run your version.

But when I ran Shawn's version (with the code as in the tutorial), there are still only single backslashes in the string for the URL. So, IMO, that suggests that double backslashes are escaped in the registry.

But I can wait till Shawn gets out the pub.

Thanks
.

Paul Black said:

Hello @OldGrantonian,

I have just checked the REG Entries in the Tutorial for you against mine, and mine are exactly the same except for . . .

Tutorial Code

Code:

[HKEY_CLASSES_ROOT\CLSID\{09A47860-11B0-4DA5-AFA5-26D86198A780}\InprocServer32]
@="C:\\Program Files\\Windows Defender\\shellext.dll"

My Registry Entry

Code:

HKEY_CLASSES_ROOT\CLSID\{09A47860-11B0-4DA5-AFA5-26D86198A780}\InprocServer32
@="C:\Program Files\Windows Defender\shellext.dll"

I only have single \ separators instead of double \\ separators. I do NOT know if that will work for you.

@Brink will be able to clarify the correct REG Entries later.

I hope this helps.

OldGrantonian said:

Thanks for trying to help. That did not add anything to the context menu.



It looks as if the double slashes are simply escapes.

I ran Shawn's reg first, without examining the results in the registry. I then ran your reg, and looked in registry. Only single backslashes were present.

Because your reg changed nothing in the registry (still single backslashes), I thought I might as well re-run Shaw's version to restore the registry to what it would have been if I hadn't run your version.

But when I ran Shawn's version (with the code as in the tutorial), there are still only single backslashes in the string for the URL. So, IMO, that suggests that double backslashes are escaped in the registry.

But I can wait till Shawn gets out the pub.

Thanks

However, I then re-ran Shawn's

Hello,

Having @="C:\\Program Files\\Windows Defender\\shellext.dll" in the REG file with the double "" in the file path is normal for it to show in the registry as @="C:\Program Files\Windows Defender\shellext.dll" with a single "" in the path. It's just one of those odd requirements for a REG file to get it to have the correct path in the registry.

OldGrantonian said:

.


With the file on the desktop, everything worked as expected.

Thanks