Jump to content

David-B

Honorary Members
  • Posts

    71
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

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

  1. Oh, yes. I totally understand and agree with you that there's an element of risk here. That said, I've dealt with annoying issues of this sort on and off for years even with Windows 10, so I'm not convinced just yet that the issue isn't being caused by something else. I know I may not seem like it, but I greatly appreciate you sharing your thoughts. Really, I do. That said, I'm rather comfortable with calling Microsoft's hardware requirements for Windows 11 nothing but a meaningless gesture to push people to buy new hardware if they want to run 11. I'm not saying I'm right, but I'm reasonably confident.
  2. My Clonezilla backup image is of Windows 11 21H1, and it was working perfectly. Since I do lots of Android-related work, I want access to the Android app integration. If I roll back, that's what I would flash.
  3. Yeah I am considering doing a rollback. I'm waiting for tomorrow's patches to roll out before I make a decision about that though.
  4. Alright. I have just submitted a ticket and included a reference to this thread. Thank you for your continued support with this, by the way. I really appreciate it especially since I am not so sure that the issue I'm facing is caused by Malwarebytes given that I have seen this occur even when I have Malwarebytes disabled.
  5. I would love to do this, but there's just one problem: the deadlock occurs arbitrarily. There is no consistent pattern for me to use for reproducing. The only way that I can think of to collect any information would be to just leave the application running in the background and wait for the machine to deadlock to see what I collect, but given that the log grows so rapidly, that seems infeasible. And even if I do go that route, that doesn't guarantee that the valuable log data wouldn't get lost when I am forced in to crashing the machine.
  6. Fair enough. The reason I had to disable the TPM is because I was working on an application that would behave differently depending on whether a TPM was present or not. Because of this, I wanted to have a way to keep getting updates regardless of whether I had it on or off at any given time. So, you are suggesting running Process Monitor on the machine in the background until it locks up again?
  7. I find it interesting that the Search Service is still corrupted. I tried fixing it earlier by forcing a rebuild of the index. Evidently that was not enough, so I have just tried the more aggressive method of totally wiping out the contents of C:\ProgramData\Microsoft\Search as per the instructions listed on the page you linked to. The "Skip TPM on Dynamic Update" thing is there because I needed to disable my TPM for a bit at one point, but doing so caused updates to stop installing because my device was not in compliance with the hardware requirements. The TPM requirement is a stupid meaningless artificial limitation set by Microsoft anyway, so I fixed it by using this. I have an explanation for the set of C:\WINDOWS\system32\_MEI* folders. One of the background services that I run on my computer is a self-built application that I wrote in Python and packaged into a Windows binary using PyInstaller. Applications built with PyInstaller generate these _MEI* directories, but they typically do it in the user's temp directory and clean them up when they are finished executing. Apparently though, the one that I'm running as a service is dropping the temporary directories in C:\WINDOWS\system32 instead and isn't cleaning them up. In other words, you found a bug in my code that I wasn't aware of. Once I get a chance to fix it, all will be well. As for the ESET log, I have attached it. As you expected, it didn't find anything. The one and only thing it did find was a false positive. log.txt
  8. As requested, here are the logs! Thank you for your continued help. FRST.txt Addition.txt
  9. Unfortunately, whatever is happening still happens even after doing this.
  10. It was offered to me, and I decided to take it. In hindsight, perhaps I shouldn't have. I can try it, but may I ask what exactly is wrong with Bonjour and CCleaner?
  11. I think this may be a dead end. I just had this issue happen again, and Malwarebytes is disabled. ☹️
  12. Hello! As requested, here is the file you requested. mbst-grab-results.zip
  13. Hello Malwarebytes Community, Last week, I updated my PC to the Windows 11 22H2 release. Soon after upgrading, I began seeing frequent occurrences of the machine arbitrarily deadlocking. The behavior is weird to describe. I would simply be using the machine, and then various applications that I have open would start locking up and becoming unresponsive. It would begin with the application that was in focus, and then in the next 30 seconds or so, would begin to impact other applications that I have open as well, ultimately ending with the entire Explorer UI becoming unresponsive. The only "solution" would be to crash the computer and reboot it. I've seen this behavior occasionally happen in the past, but it has become a regular occurrence averaging about 5 times a day since updating to 22H2. I've had bizarre issues with installing major updates in the past that stem from Malwarebytes, so I naturally I assumed that Malwarebytes is the culprit. Because of that, I've been A/B testing the use of my machine with and without Malwarebytes enabled. The issue has never occurred when I have it disabled. Is anyone seeing bizarre behavior of this sort? Is the issue known about among the Malwarebytes team? Is there something I can do to work around it? Or should I just run my system without Malwarebytes until an update is released?
  14. @exile360 Are you running a preview release of Chrome? As far as I understand, this feature never made it to the stable release.
Back to top
×
×
  • 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.