Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Software Troubleshooting
Win 10 No Safe Mode, Login to black screen
Message
<blockquote data-quote="bradcarvey" data-source="post: 625631" data-attributes="member: 61517"><p>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.</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>The response the current support ticket was as follows:</p><p></p><p><em><span style="color: #336600">You can copy the DBL.db from the drive that is effected and put it into another unmanaged system to see what was removed.</span></em></p><p><em><span style="color: #336600">From this you would be able to create copies of the files that were removed in an attempt to restore the profile.</span></em></p><p></p><p>I found the file in ProgramData\WRData</p><p>dbl.db 4/24/2017 3:16 PM 45,050 KB</p><p></p><p><span style="color: #b30000">"put it into another <em><u>unmanaged</u></em> system to see what was removed" ?????</span></p><p></p><p><span style="font-size: 22px">Suggestions on what this means?</span> </p><p></p><p></p><p>I copied the dbl.db to C:\ProgramData\WRData on a new install of Webroot on a windows 8.1 HP spectre.</p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="bradcarvey, post: 625631, member: 61517"] 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: [I][COLOR=#336600]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.[/COLOR][/I] I found the file in ProgramData\WRData dbl.db 4/24/2017 3:16 PM 45,050 KB [COLOR=#b30000]"put it into another [I][U]unmanaged[/U][/I] system to see what was removed" ?????[/COLOR] [SIZE=6]Suggestions on what this means?[/SIZE] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
