Jump to content

John L. Galt

Experts
  • Posts

    3,105
  • Joined

  • Last visited

Everything posted by John L. Galt

  1. Hi, MB for Fx is blocking hxxp://www.irfanview.info/files/iview453_x64.zip (URL altered even though I know it is not dangerous): Virustotal only shows Yandex as detecting anything wrong: https://www.virustotal.com/gui/file/941056da4f50df44eeef46ca875255bd3d09c3aaf1bdfffad5f65de0a515ff02/detection
  2. Hi, The MB addon for Firefox is blocking Zabkat, maker of Xplorer² File Manager and a few other utilities. Details: Windows 10 X64 Pro Insider Preview (Skip Ahead) Version 1903 (OS Build 18941.1001) Firefox Nightly ver 70.0a1 (2019-07-23) (64-bit) MB Browser Extension for Fx ver 1.0.44 When I tried to go to ZabKat site to check for an update and make another report elsewhere, I received this: moz-extension://1cd69040-a68e-421e-b311-c14bd0bda41b/redirects/blockedMalware.html?url=https%3A%2F%2Fwww.zabkat.com%2F&host=www.zabkat.com&type=malware&subtype=reputation If you need any more info, please let me know.
  3. Please note: This forum is titled General Chat because it is meant for just that - general chat. This forum is NOT where you need to post if you have concerns that you might be infected - there is a separate forum for that. Please read the following post, which @David H. Lipman posted above, in its entirety, and follow the instructions explicitly to get malware removal help. Again, Malware removal help is not performed outside of the Windows Malware Removal and Help forum, in which the above post is located.
  4. Yeah, if it is software, this should (hopefully) lead to a quick fix. If not, we'll be here.
  5. If you were able to try restoring the files in MB3, then that means you're able to make out at least some of the things on the screen, correct? My next suggestion would be to visit your GPU's website (or your computer manufacturer's website) to find the appropriate drivers for your GPU and the OS that you are running, and install those. If that does not solve the problem (and I suspect it will not) then you have to troubleshoot to see if it is, indeed, the GPU, or if it is possible your monitor, that is having issues. And if the drivers do not work, please let us know so a Moderator can move this topic to the General PC Help forum for further help.
  6. I've asked one of the resident Windows 10 Experts over at tenforums if it may be possible, using a conglomeration of 1 or more tutorials there, to grab the English 18329 Pro build and apply a language pack to it to get you to be able to install 18329 Pro PL-PL that you would basically make yourself. One other thought, though - you could still use the UUPDump site to download the previous build (18317) or any other build that *is* available for PL-PL at the Pro level and manually install from USB (which should have no problem being installed, IIRC), thereby fixing your MB3 protection until either M$ releases the Pro PL-PL build of 18329, or else releases a new build that has Pro PL-PL... Though that might also be an adventure in and of itself lol...
  7. Cool, I wasn't sure if it was the Beta or stable. Glad to know *both* are working much better with 18329 than they did with 18323. My desktop (the newest machine I have) is a original generation Core i7 965 EE based machine, whose BIOS was last Updated in 2011 as well. But I've upgraded just about every other component in it (same PSU since I built it in 2011, same case, and same KB - that's it lol). I'm still in the process of finishing up the clean install of 18329 on it, but I'm happy to know I can install either stable or Beta and have it working correctly.
  8. You can DL the files and make the .ISO yourself, and then mount the .ISO in Windows Explorer and run setup from there, performing essentially the exact same as the WU provided upgrade. See https://win10.guru/how-to-get-windows-insider-fast-ring-iso-for-latest-build/ for instructions, or you can PM me and I'll walk you through the steps. I've been using this site for a long time to make .ISOs and manually install upgrades instead of using WU because WU is, at best, unpredictable, and at worst, a complete nightmare. --- Clean installed, setting up drivers and apps, then making a Macrium backup and then will clean install the latest MB3 I have downloaded, and then see how it works.
  9. I will be clean installing Windows 18329 directly on my machine in the next several hours, and as soon as I get a direct link for the new 2831 build (MB 3.7.x) I'll clean install that as well onto that clean OS install and see how it goes.
  10. Others are also reporting the same. I'm clean installing 18329 tonight / tomorrow, we'll see how it goes.
  11. Although, these days it seems as if it is by the truckload....
  12. Same here - after install, now 2 / 4 are working. A step in the correct direction
  13. I had a feeling it was something along those lines. The use of the .DLL and the appended string for the unattended setup caught the key in the Setup log. Not cool. I'd like to make a suggestion about the batch file - for files larger than 20 MB, I get the instructions, but the first time I clicked to have wetransfer open the batch file exited, thereby removing the instructions on how to send the file. Can you maybe add another pause (and / or prompt asking the user if he has successfully sent the file) before exiting out of the instructions (assuming you continue to use this batch file for other purposes, which it seems like you do)? After rebooting I ran it again, it gave me a whopping 100 MB file (I think because I also opened Firefox while the PM was running, trying to get ahead of the batch file). This time I copied the instruction and pasted them to a notepad window so I could read them and complete them correctly.... Interesting. Build 18323 already has some other issues - including a very slow loading of non-M$ / non-UWP apps because of a new service entry calls Windows Insider Service (wisvc) which is described as but which has never cause problems before. On this reboot, I had just disabled that service, and it did nothing to help with MB3 loading. Others are also experiencing GSODs and issues with audio (which I am not). But I can fully test anything that you guys want to suggest - I have Macrium backups already in place from before *and* after the upgrade to 18323.
  14. I got 2 logs because I ran into the same problem ch3mn3y - it wasn't actually on my desktop. The first log is 35 MB, the second is over 100MB. I'm including the second one as it was off a reboot.
  15. Yeah, it is intriguing why it only happens when the support tool does it's automated uninstall / clean and reinstall. My Setup logs have no mention of my license, but that is really the first thing that I did after installing, just so I could check with the premium version on the compatibility issues with WinX IP Build 18323. There is probably (hopefully?) a simple fix in the coding of the tool.
  16. Lol, well, technically, it seems (from the evidence so far) that it actually *did* do just that. However, it seems the setup log picks up on the forced insertion of the license. Or else, the supposed config file *is* the setup log? 🤨
  17. I'm almost positive that they do - this is how the support tool originally evolved, to allow users to be able to uninstall MBAM, clean all traces of it, and then reinstall, and it would (originally, IIRC) save the license info into a .TXT file on the desktop. I want to say that was with MBAM ver 2.x when it worked that way, versus the newer support tool not actually saving to the desktop (which most users would not delete those files, which I found in more than a few clients' machines after they had attempted to self-repair before coming to me). Bingo. If you hadn't mentioned it, I wouldn't have bothered checking - but knowing what the process is of the support tool, I already knew that I wasn't going to walk through the clean reinstall process because my install was a clean install to begin with.
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.