Jump to content

RTL434

Members
  • Content Count

    77
  • Joined

  • Last visited

About RTL434

  • Rank
    Regular Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks. O.K. now with 1.0.15048.
  2. Have used TreeSizeFree for a while now with no problems. I currently have version 4.3.1.494 installed. Was informed today that there is an update available---4.4. I downloaded it but when I tried to run it, MWB quarantined it. Uninstalled 4.3 and then re-installed it. No problem there. Don't know if this is a false positive or what. Ran the False Positive tool but it didn't find anything to report. Would like an opinion on this. Report attached and downloaded file also in zip format. TreeSize_Trojan_Report.txt TreeSizeFreeSetup.zip
  3. When I "Check for Updates" on my four machines it downloads a new Version 1.0.718. Can't see any info as to what it fixes anywhere in the Forum.
  4. Well said @TempLost. My feelings exactly.
  5. @LiquidTension Hello, Have updated all my PC's to the latest beta 4.0.3.48. Have run the sequence twice as per Post#8 on the two PC's that were getting the C35 errors. They are now clean-- no problems.
  6. @LiquidTension No the error does not seem to be consistent. I powered this PC up at 07:34 this morning and it had the error. Powered up at 11:06 to do as you requested and it didn't show the error. I installed the 4.0.2.44 on all my three desktops and laptop yesterday. Desktop 3 and the laptop are fine. Desktops 1 and 2 show the error. I have run your request twice on both those PC's. C35_errors_test_sequence_report.docx EventLogsDesk1.zip mbst-grab-results-Desk1.zip C35_Errors.zip EventLogsDesk2.zip mbst-grab-results-Desk2.zip
  7. I had seen the new beta release but wasn't sure what release it was and had PM'd Erix for clarification. Then I saw Jekko's response in another post. Am now running on it. BTW if we're going to be pedantic---it should be " 1 zip too much " . ☺️
  8. @LiquidTension, Looks like my component package is now at 1.0.690. Must have updated just lately as it was at 1.0.682 in this morning's scan report.
  9. @LiquidTension, I'm seeing the error as well in that location throkr calls out----and I'm not doing Restores at the time. Currently on Win 10 1903 18362.387 and 4.02.41 1.0682 1.0.13531. Everything seems normal. Have also set Event Log on in MWB. mbst-grab-results.zip EventLogs.zip.zip
  10. No you're not losing your mind. I saw this a couple of times. It was while I was on the Free Version prior to activating my licence. I took it to be a plug for a Free User to upgrade to Premium. Since this is a beta and they might be using a different name when it goes live, they are using Wossname as a placeholder.
  11. Update. On Saturday 14th. Sept. I removed 4.0.1 and reverted to 3.8.3 as I wasn't sure what would happen in the meantime if I received Windows Updates and they got screwed up because of the restart problem. Ran like that until the 20th.---no problems. On Friday the 20th. a new version was shared in private and that fixed the problem. Still running on it and restarted numerous times.
  12. Hi @LiquidTension Thanks for the update, appreciated.
  13. @LiquidTension Hello, I had a problem this morning when I powered up. Forced a Dump. PC came up after it had created the dump file. No problems since and have used the PC for the last three and a half hours. 14th_September.docx mbst-grab-results.zip
  14. @LiquidTension Hello, have done as requested (hopefully) and results are attached. 12th_September.docx mbst-grab-results.zip
  15. @LiquidTension Restored back to normal. Updated Windows and did an "Update & Shutdown" as opposed to a Restart, Came up and now at 18352.356. Set MP ON. Powered off and then on. Came up fine. Did a further two and no problems. Did a Restart and the problem is there. Reset and it came up. Did a further two PD/PU's and they were fine. So it definitely looks like a Restart is what screws it up-----only on 4.0.1! Will do further checks tomorrow as time is getting on. Didn't bother running the tool for the logs as the previous entry logs should have the data.
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.