If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Stubborn File - Can't Delete
Moved Google Pro to a different folder location and
C:\Program Files (x86)\Google\Update\1.3.33.5\ ... ... GoogleCrashHandler64.exe ( old location ), won't delete. All security parameters have been set to full control etc., but NG. Tried File Assisin. No big deal as it causes no real harm. but I like things neat and tidy. Any help appreciated and thanks. |
Ads |
#2
|
|||
|
|||
Stubborn File - Can't Delete
SteveGG wrote:
Moved Google Pro to a different folder location and C:\Program Files (x86)\Google\Update\1.3.33.5\ ... ... GoogleCrashHandler64.exe ( old location ), won't delete. All security parameters have been set to full control etc., but NG. Tried File Assisin. No big deal as it causes no real harm. but I like things neat and tidy. Any help appreciated and thanks. Are you sure that isn't currently loaded and being used ? Google Update is only supposed to remove itself, if all Google products are removed. It's possible something there runs as a service or the like. Multiple Google products could call on that for update services. I don't know exactly how to uninstall it - it may or may not have a separate entry in Programs and Features. ******* Pendmove/Movefile uses the same OS features as the OS Windows Update logic. It can schedule a file for deletion on a reboot. It if was running as a service, the services could be shut down at that point, making removal possible. https://docs.microsoft.com/en-us/sys...oads/pendmoves If it was a service or loaded as a Startup Item, then you might see a dialog once you've deleted it. You could use Sysinternals Autoruns ahead of removing it, to check to see whether it's wired up in there somewhere. Autoruns lists the various Startup methods all in one big list. Once you've disabled it in Autoruns, you can then attempt to delete the file. https://docs.microsoft.com/en-us/sys...loads/autoruns If any other Google products attempt to call that service, then... tough :-) They probably won't fall over, on the attempt. Paul |
#3
|
|||
|
|||
Stubborn File - Can't Delete
On 9/11/2017 9:20 AM, Paul wrote:
SteveGG wrote: Moved Google Pro to a different folder location and C:\Program Files (x86)\Google\Update\1.3.33.5\ ... Â*Â*Â*Â*... GoogleCrashHandler64.exe ( old location ), won't delete. All security parameters have been set to full control etc., but NG. Tried File Assisin. No big deal as it causes no real harm. but I like things neat and tidy. Any help appreciated and thanks. Are you sure that isn't currently loaded and being used ? Google Update is only supposed to remove itself, if all Google products are removed. It's possible something there runs as a service or the like. Multiple Google products could call on that for update services. I don't know exactly how to uninstall it - it may or may not have a separate entry in Programs and Features. ******* Pendmove/Movefile uses the same OS features as the OS Windows Update logic. It can schedule a file for deletion on a reboot. It if was running as a service, the services could be shut down at that point, making removal possible. https://docs.microsoft.com/en-us/sys...oads/pendmoves If it was a service or loaded as a Startup Item, then you might see a dialog once you've deleted it. You could use Sysinternals Autoruns ahead of removing it, to check to see whether it's wired up in there somewhere. Autoruns lists the various Startup methods all in one big list. Once you've disabled it in Autoruns, you can then attempt to delete the file. https://docs.microsoft.com/en-us/sys...loads/autoruns If any other Google products attempt to call that service, then... tough :-) They probably won't fall over, on the attempt. Â*Â* Paul Why not delete it from a Linux live CD? Rene |
#4
|
|||
|
|||
Stubborn File - Can't Delete
Rene Lamontagne wrote:
On 9/11/2017 9:20 AM, Paul wrote: SteveGG wrote: Moved Google Pro to a different folder location and C:\Program Files (x86)\Google\Update\1.3.33.5\ ... ... GoogleCrashHandler64.exe ( old location ), won't delete. All security parameters have been set to full control etc., but NG. Tried File Assisin. No big deal as it causes no real harm. but I like things neat and tidy. Any help appreciated and thanks. Are you sure that isn't currently loaded and being used ? Paul Why not delete it from a Linux live CD? Rene Yeah, that'll work. If there was an "uninst" in the folder or some other trick, there might be a better way to remove it via Windows. I don't know if that Google crap is intended to remove easily or not. I don't really believe the statement that it "gets removed when the last Google product is removed from the OS". That sounds so... unlikely. So I tossed a couple file names into a Google search, these two... C:\Program Files (x86)\Google\Update\1.3.33.5\npGoogleUpdate3.dll --- A Firefox plugin C:\Program Files (x86)\Google\Update\1.3.33.5\GoogleCrashHandler.ex e --- ??? Really? and it really is messy to deal with. While this has some suggestions, I'm not getting a "strong theme" as to how this works, whether it has multiple vectors, or what's going on. It almost looks like the Google application it is "helping", helps to put it back. And it seems to be hacking the browser to get its own way. https://www.ghacks.net/2012/07/17/cu...how-to-remove/ Their Task Manager shows an EXE running - is that in that folder too ? https://cdn.ghacks.net/wp-content/up...ng-windows.png "GoogleUpdate.exe" x32 Paul |
#5
|
|||
|
|||
Stubborn File - Can't Delete
Don't know why but after a reboot, all was gone.
|
#6
|
|||
|
|||
Stubborn File - Can't Delete
SteveGG wrote:
Don't know why but after a reboot, all was gone. Next time, you can run "PendMove" in the example, and get back a list of things "scheduled to be removed". If it "disappeared on a reboot", that's how it happened. It was put into a queue for removal. And with the Sysinternals tool, you can find out what is in the queue to be processed. Once you reboot, the file will be gone, and the queue (slightly) cleared. I've seen crap left in the queue, with no explanation of why it is still there. And the reason for doing it that way, is if some services (with dependencies) is running and it's not possible to stop it - they need a way to deal with that. During shutdown or startup, such services might not be running, and that's when the delete happens. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|