Jump to content

Soozy

Honorary Members
  • Posts

    116
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Soozy

  1. Now oddly, this is what shows in a right click item menu in dark mode.
  2. I may use dark mode, but on Edge I use a color theme and the MB icon is still white.
  3. Same here with Browser Guard on Edge. Also noticed the Browser Guard icon changed from blue to white.
  4. As I've been told since July, MBAM will not fix issues if you are using a Windows Insider build.
  5. If I changed my settings to the below Malwarebytes 5 opens as it should. I can also resize the window and it stays.
  6. Same issue here. The right side of the window is always off the screen, at least the X is. My screen resolution is 1920X1080 and running Windows 11.
  7. Curious why the need to deactivate the Premium License and uninstall older version. I updated to Premium Beta right over the previous version with no problem>
  8. Just tested this again today and the build update is still failing unless the above workaround is used.
  9. Same here. The component package updated but not the Version.
  10. I am also on Windows 11 Build 25262 and the Component package is correct, but the Version will not change.mbst-grab-results.zip
  11. I've seen those threads already as I am a MS Volunteer Moderator and an WIMVP. My issue updating a full build started in July. The source of the problem was found by a MS Dev looking at my failed update logs. Per MS: MWB is locking out permission to files the servicing operation needs. Since the files aren't accessible by the OS, the update fails. This issue was reported by myself here and the MS Dev to MBAM. I have no problem using the workaround, but would like to see the issue acknowledged on the MBAM side and not just get the "well it's a MS Dev build they have problems". Sorry for the rant.
  12. For those running Dev Channel Windows 11 builds the solution is a workaround, not a fix. I tried the Windows 11 update again last week leaving MBAM on and it failed again with the same error. Only the 2nd time in 8 years I've had a long bug issue between MS and MBAM.
  13. Disabling MBAM worked like a charm and the Dev build 25201 updated with no problem.
  14. Yes, Microsoft Dev builds can have issues, but the Dev nailed this update problem down to something MBAM was blocking.
  15. Wish I knew if the new Beta fixed the Microsoft update issue.
  16. The Insider Dev Team reported this directly to MBAM, so hopefully it gets fixed quickly. Thanks for the tips, I was just going to turn off the Protections.
  17. Since 6-29-22 I have had an ongoing issue with Windows 11 Dev Channel builds failing with the error code ox8007000d. I've clean installed several times, gone back to a Beta build, updated to Dev build fine, but then the next one fails. I've been working with the Windows Insider Team and they discovered the problem.This is what they said: MWB is locking out permission to files the servicing operation needs. Since the files aren't accessible by the OS, the update fails. My current MB is 4.5.14 - 1.0.59845 - 1.0.1761. With the next Dev Win 11 build I will try just disabling MB and see how it goes.
  18. Just wanted to give all a head's up that as of right now MBAM is performing great on Windows 11 in the Dev Channel.
  19. The word is that this issue is fixed on Insider Build 20246 released today.
  20. That was fun. LOL Let's try this: https://we.tl/t-8th51hZ20M
  21. I hope I did this correctly. https://we.tl/t-eHwtzsIGfp
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.