bradcarvey

Level 1
Lots going on, will post from a computer later. 24 hours later, webroot responded with better instructions and closed my case. I talked to a friend yesterday, about the problem. He knew all about it and asked if he could have a look at the drive. He is not an IT guy, but is data security expert. Certainly, one of the best in any government research lab. This should be interesting.

I will follow ghost later today...

Brad Carvey
 

shmu26

Level 83
Verified
Trusted
Content Creator
Lots going on, will post from a computer later. 24 hours later, webroot responded with better instructions and closed my case. I talked to a friend yesterday, about the problem. He knew all about it and asked if he could have a look at the drive. He is not an IT guy, but is data security expert. Certainly, one of the best in any government research lab. This should be interesting.

I will follow ghost later today...

Brad Carvey
Thanks for update
 
  • Like
Reactions: Amelith Nargothrond

bradcarvey

Level 1
Learned a lot of stuff today and yesterday. At the end of this, I will try to write a summary, so if others have this problem, this thread might be able to help them.

I got a second response from webroot, regarding my support ticket. The first response listed methods that assumed I could boot into window and run programs. If a computer got effected by the webroot issue, there would be not way to boot and run programs. Plus, the answer was targeted at a company with lots of corrupted systems. The second answer was targeted more at an individual, but even though my response made it clear that I could not boot and run programs, they suggested that I should run Webroot and then unblock the block files. This was when I realized that nothing I could do would fix the problem. At boot up, Webroot was correcting any fixes, because it was still running and still saw those system files as corrupt. Therefore, Webroot would block and effort to fix the "blocked" system files. Very frustrating.

After the second response that required being able to boot the corrupted window 10 drive, Webroot declared my problem fixed and closed the support ticket.

So I started another support ticket and this time I got something that might help. Although, if webroot would just tell us what files were blocked, it would make is much easier to fix those files. Then I could figure out a way to boot without webroot and things should work.

The response the current support ticket was as follows:

You can copy the DBL.db from the drive that is effected and put it into another unmanaged system to see what was removed.
From this you would be able to create copies of the files that were removed in an attempt to restore the profile.


I found the file in ProgramData\WRData
dbl.db 4/24/2017 3:16 PM 45,050 KB

"put it into another unmanaged system to see what was removed" ?????

Suggestions on what this means?


I copied the dbl.db to C:\ProgramData\WRData on a new install of Webroot on a windows 8.1 HP spectre.
I opened webroot and could not find anything that suggested there was a way to look at the dbl.db file. I then ran a scan, but it found nothing and there is not way to view the dbl.db file from Webroot.

Perhaps they want me to do a diff to see the difference, but there is nothing to check it against. Plus it's not an ascii file, what good would that do.

Maybe if I open the database file and look at the last entry there will be some information, but what do I open it with and what good would that do.

BTW, once I figured out that webroot was destroying any fixes at boot time, I was able to get to get a startup options in advanced options. But Safe Mode stalled, just like a regular boot. I now know that I safe mode was meaningless, because webroot was blocking system files and safe mode would have no effect on that.

I am not going to work on this more this evening. Tommorrow, I will experiment with removing the file from my corrupted folder and possibly more files from the WRdata folder. This may cause webroot to crash or at least not fix the blocked files. This probably won't help, but it might give me some clues to what is happening.
 
  • Like
Reactions: shmu26

bradcarvey

Level 1
Unmanaged system. Probably means a system that does not have webroot. I assume if I open the db file, it will contain records, which include blocked files. Then I can copy those files to the corrupted disk and it should boot normally, as long as I prevent webroot from blocking them.

Brad Carvey
 
  • Like
Reactions: shmu26

angustaver

Level 4
Verified
You must use linux cd live or hirens boot disk
Then delete files from the antivirus
Then with dvd Windows 10 fix windows startup
(Repair windows startup
Or with cmd commands bootrec.exe, fixboot etc ...)
When it can boot windows
Install dvd install windows 10 version 1703
And update
 

bradcarvey

Level 1
I have tried to open the DBL.db file that I copied from the WRDATA folder.
I tried using Libre Office base.
I tried excel.
I tried a variety of sql views and online views.
I have not tried Mongo or other data base programs.
I have done this in Linux and in Window 8.1.
I will try microsoft office on a mac and any other database programs on the mac.

Any suggestions? I have emailed support and asked them what I need to open their .db file.

Brad Carvey
 
  • Like
Reactions: shmu26