a registry removed

%3CLINGO-SUB%20id%3D%22lingo-sub-1590428%22%20slang%3D%22en-US%22%3Ea%20registry%20removed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590428%22%20slang%3D%22en-US%22%3E%3CP%3Emy%20current%20Edge%20Version%20is%2085.0.564.30%20(Official%20build)%20beta%20(64-bit)%2C%20i%20do%20not%20know%20why%20the%20following%20registry%20has%20been%20removed%20by%26nbsp%3BJunkware%20Removal%20Tool%20(JRT)%20by%20Malwarebytes%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7BSuccessfully%20deleted%3A%20HKLM%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CExplorer%5CBrowser%20Helper%20Objects%5C%7B1FD49718-1D00-4B19-AF5F-070AF6D5D54C%7D%20(Registry%20Key)%3CBR%20%2F%3ESuccessfully%20deleted%3A%20HKLM%5CSoftware%5CWow6432Node%5CMicrosoft%5CWindows%5CCurrentVersion%5CExplorer%5CBrowser%20Helper%20Objects%5C%7B1FD49718-1D00-4B19-AF5F-070AF6D5D54C%7D%20(Registry%20Key)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1590450%22%20slang%3D%22en-US%22%3ERe%3A%20a%20registry%20removed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590450%22%20slang%3D%22en-US%22%3E3rd%20party%20programs%20that%20claim%20to%20be%20cleaning%20registry%20can%20mess%20up%20Windows%2010%20pretty%20bad.%20Windows%2010%20actually%20does%20not%20need%20those%20sort%20of%20programs.%20if%20you%20wanna%20know%20why%20they%20removed%20it%20you%20can%20ask%20malwarebytes%20since%20they%20made%20the%20program.%3CBR%20%2F%3E%3CBR%20%2F%3Eusing%20programs%20like%20this%20or%20ccleaner%20which%20is%20the%20same%2C%20can%20cause%20further%20problems%20in%20the%20future.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1590631%22%20slang%3D%22en-US%22%3ERe%3A%20a%20registry%20removed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590631%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310193%22%20target%3D%22_blank%22%3E%40HotCakeX%3C%2FA%3E%26nbsp%3Bthis%20is%20news%20to%20me%20%2C%20thank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1590643%22%20slang%3D%22en-US%22%3ERe%3A%20a%20registry%20removed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590643%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325577%22%20target%3D%22_blank%22%3E%40MarsMas%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BI%20can%20only%20speculate%20as%20to%20why%20Malwarebyte's%20JRT%20removed%20registry%20entries%20to%20those%20particular%20Helper%20Objects.%26nbsp%3B%20I%20do%20know%20that%20Helper%20Objects%20are%20frequent%20targets%20for%20malware%20redirection%20and%20it%20is%20possible%20that%20is%20what%20JRT%20detected.%26nbsp%3B%20I%20don't%20know%2C%20though.%26nbsp%3B%20As%20Skylar%20suggested%2C%20the%20question%20might%20be%20addressed%20in%20Marlwarebytes%20technical%20forums.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20writing%20primarily%20to%20let%20you%20know%20that%20%3CA%20href%3D%22https%3A%2F%2Fwww.malwarebytes.com%2Fjunkwareremovaltool%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EJRT%20is%20discontinued%20software%3C%2FA%3E.%26nbsp%3B%20EOL%20was%26nbsp%3B%20April%2026%2C%202018%2C%20and%20the%20product%20is%20no%20longer%20supported.%26nbsp%3B%20Malwarebytes%20suggests%20moving%20to%20ADW%20instead.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20sure%20that%20either%20is%20the%20best%20way%20to%20approach%20the%20issue%2C%20however.%26nbsp%3B%20It%20seems%20to%20me%20that%20the%20better%20solution%20is%20to%20stop%20malware%20before%20the%20computer%20is%20compromised.%26nbsp%3B%20I%20use%20Malwarebytes%20Premium%20as%20a%20compliment%20to%20Windows%20Security%2C%20and%20have%20found%20that%20the%20two%20products%20work%20well%20in%20tandem%2C%20coming%20at%20attack%20detection%20from%20different%20directions.%26nbsp%3B%20I%20haven't%20had%20an%20issue%20in%20years%20using%20that%20combination%20on%20my%20four%20primary%20Windows%2010%20computers%2C%20so%20I%20no%20longer%20use%20tools%20similar%20to%20JRT%20or%20ADW.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1590647%22%20slang%3D%22en-US%22%3ERe%3A%20a%20registry%20removed%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1590647%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318339%22%20target%3D%22_blank%22%3E%40tomscharbach%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Every%20good%20thank%20you%2C%20i%20already%20have%26nbsp%3B%3CSPAN%3EMalwarebytes%26nbsp%3Band%20will%20keep%20it%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

my current Edge Version is 85.0.564.30 (Official build) beta (64-bit), i do not know why the following registry has been removed by Junkware Removal Tool (JRT) by Malwarebytes, 

 

{Successfully deleted: HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{1FD49718-1D00-4B19-AF5F-070AF6D5D54C} (Registry Key)
Successfully deleted: HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{1FD49718-1D00-4B19-AF5F-070AF6D5D54C} (Registry Key)

4 Replies
Highlighted
3rd party programs that claim to be cleaning registry can mess up Windows 10 pretty bad. Windows 10 actually does not need those sort of programs. if you wanna know why they removed it you can ask malwarebytes since they made the program.

using programs like this or ccleaner which is the same, can cause further problems in the future.
Highlighted

@HotCakeX this is news to me , thank you

Highlighted

@MarsMas   I can only speculate as to why Malwarebyte's JRT removed registry entries to those particular Helper Objects.  I do know that Helper Objects are frequent targets for malware redirection and it is possible that is what JRT detected.  I don't know, though.  As Skylar suggested, the question might be addressed in Marlwarebytes technical forums.

 

I'm writing primarily to let you know that JRT is discontinued software.  EOL was  April 26, 2018, and the product is no longer supported.  Malwarebytes suggests moving to ADW instead.

 

I'm not sure that either is the best way to approach the issue, however.  It seems to me that the better solution is to stop malware before the computer is compromised.  I use Malwarebytes Premium as a compliment to Windows Security, and have found that the two products work well in tandem, coming at attack detection from different directions.  I haven't had an issue in years using that combination on my four primary Windows 10 computers, so I no longer use tools similar to JRT or ADW.

Highlighted

@tomscharbach 

very good thank you, i already have Malwarebytes and will keep it