Skip to main content
To Customer Support To Customer Support
Does Webroot disable Windows Modules Installer? Receiving MSE error 0x80070424 after install

 

Greetings!  I'm new to the Webroot Community - experiencing first install of Webroot SecureAnywhere just yesterday. The install seems to have triggered a scuffle in the sandbox between WSA and MSE, however, and MSE is now acting like a crybaby, making demands that its service should be restarted and then whining that the service couldn't be started, mumbling through tears something about the specified service does not exist as an installed service, with Error code: 0x80070424 topping off the tantrum. 

 

Now, for the record, I have no issue with kicking MSE out of the sandbox completely and allow WSA the entire playground, but I am curious as to the origins of the MSE issue now in play. Here's a recount of events following install of WSA:

  

The results returned from the initial system scan identified two threat events; the removal of both threats being highly recommended. I followed the recommendation and initiated the cleaning process. I think that the cleaning crew that was dispatched to disinfect my system files might have been under the influence of one too many double shot expressos, or maybe just fanatical about work performance, because it appears that not only did they get my system squeaky clean, but perhaps tossed out some MS files with the bathwater as well... as, (see above), MSE can no longer be started.

 

I have the WSA log of cleanup operation. Is there someone to send it to?  Is somebody able to look it over? I would like to know if the process executed properly or if there might be indication of files being deleted in error or some corruption that needs to be addressed and/or repaired. (I am also down with doing a corrected uninstall of MSE, if warranted.)

 

Basic system info:  Windows 7 Ultimate 64-bit

 

Thanks so much!

 

 
Hi kimberleyc

 

Welcome to the Community Forums.

 

Given you are using WIndows 7 Webroot should have all relevant Windows components recorded in its Cloud database and so I would suspect that WSA is not the cause...but a quick way to check is to shutdown WSA temporarily and see if the issue persists. You can do that by right clicking on the notification tray icon and selecting 'Shutdown protection' and then following the on screen instructions to complete the process.

 

Then try repeating the activities that yo are having issues with.

 

Either way I would recommend that you Open a Support Ticket so that the Support team can take a look at the issue for you, and to whom you can send you information to as and when they ask you for it if you let them know that you have it.

 

Hope that helps?

 

Regards, Baldrick
Thank you for the direction - hopping right on it!
Update: I did follow your instructions, to no avail... on both counts. My attempt to rectify the issue had no affect, and, rather disappointingly, I have yet to receive a response to my support ticket.
Hi kimberleyc

 

It can take some time for the Support Team to respond as it depends on what other sorts of issues are in the queue. If they have not responded by now please post back and we can try to see if we can find out why that is.

 

Regards, Baldrick

Reply


Terms & Conditions