Replies

This has worked for me

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USER\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}]

Never Say Never

Did you run it on the user account you are logged into? Sounds like you probably added it to your “Administrator account”

Never Say Never

Do have dropbox or similar? On many machines with dropbox I notice that and don’t even attempt to fool with them until the syncing is done

Never Say Never

1 user thanked author for this post.

Kenneth Stephens

Guess that depends on the type of files. What I would do is freeze Backblaze until it’s sorted. Then I normally copy data files and such that are needed immediately after re-install and after scanning with multiple programs. Then after a bit of time passes and scanning again I move everything back. Also note that if he or Backblaze have copies of files from BEFORE the suspected hack, those should be safe, but I’d still scan them to be sure.

Never Say Never

Barry,

Make sure you don’t have any other McAfee stuff like web advisor causing issues. Then you might consider re-installing McAfee and using Revo and/or the MCPR tool. You may have had a glitch when you uninstalled.

I usually use Revo, reboot, then reboot again and run the MCPR tool, sometimes even twice for good measure. I have never had it complain about not connecting to server, even when run offline.

Good luck!

Never Say Never

Have you tried running it in safe mode? I always right-click the file, check “unblock” at this file came from another computer and click apply. Then right-click the file and choose run as administrator

Never Say Never

RetiredGeek wrote:

When does he get his Tile and GoPro?

Ha! Wish I’d have had a gopro on Renegade years ago shortly after we got him. Seems he jumped a big buck in the woods, as evidenced by the hoof mark on his hip. He was in BAD shape. Almost put him down twice, especially after he passed about a pint or two of blood, but he wasn’t crying in pain, so decided to work him through it. Had to massage his bladder a few times a day to have him go. Was a rough time for sure, but he made it back and doesn’t even limp any longer.

Never Say Never

This is weird. Trying to name new pup. Checking his records, he was born May 26. Renegade (my 5-y/o) was born May 26. People that had him for a week nicknamed him Hank. Hank Williams Jr was born May 26. He has that attitude too!

Too many coincidences to ignore, so he’s officially christened Bocephus.

Never Say Never

1 user thanked author for this post.

Myst

Logged in remotely to a client’s machine Win11 22H2 and it was waiting for a reboot to install. Get the latest updates is OFF and updates were paused. Quick reboot, then installed this month’s updates. Sat at 70-71% installing for quite some time, then Updating Windows at 0% “Don’t turn of your computer” for a good bit of time. Ended up at about 1hr to install latest updates. Something is weird this month!

Never Say Never

Updated 1 Win 11 and 1 Win 10 with no observed issues. Then updated my Win11 workstation and it sat forever at 70-71% installing, then after reboot hung at “installing 0% done” for quite a bit.  All in all took about 50 minutes. Much longer than normal but everything seems to be working fine.

Never Say Never

2 users thanked author for this post.

arbrich, Microfix

Just skimming through I didn’t see if you mentioned if you have a video card. If so, could you try removing and testing with onboard video?

Never Say Never

1 user thanked author for this post.

Microfix

Yep. One of the first things I do now is check and decrypt the drive on new machines.

Never Say Never

1 user thanked author for this post.

PKCano

Easiest way is go ahead and connect to internet. When it gets to entering your address for your ms account type in no@thankyou.com. Use anything for a password. It will fail and give you option to create local account.

Never Say Never

1 user thanked author for this post.

Fred

I’m really getting tired of MS and Windoze!

Never Say Never

If you have a backup of C:\Users\UserName\AppData\Local\Google\Chrome\User Data\Default the passwords are stored in a file Login Data. Copy it over and you should have them back. I always backup that folder for clients using Chrome

Never Say Never

1 user thanked author for this post.

Pepsiboy