gjm

Established Members
  • Content Count

    64
  • Joined

  • Last visited

  • Days Won

    2

gjm last won the day on May 16 2020

gjm had the most liked content!

Community Reputation

2 Neutral

2 Followers

About gjm

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. gjm

    3.5.x Beta

    Downloaded and installed 45966. Magnets no longer load, advising uTorrent is already running. I can download torrent files. These do not work if double-clicked (file associations are set up) but *do* work if dragged to the uTorrent client. Tried the suggested route of opening the .exe and simply cop[y/pasting the uTorrent file - it's not there.
  2. gjm

    3.5.x Beta

    So this'll be the 'full' version with all the added, and unwanted stuff. I wan to test and prove improved versions. Not fight through the rubbish. Please post links to 'clean' beta versions.
  3. gjm

    3.5.x Beta

    I've gone back to 45852. I was having issues with 45912. Every time I started it, I was warned of an older version. I couldn't load magnets. Loading a torrent resulted in a warning that another version of uTorrent was already running. OK... I'm not running rafi's versions or tweaks - I'm trying the 'vanilla' out-of-the-box version. It's what Beta-testers do!
  4. gjm

    3.5.x Beta

    Tried to install 45918 as a user - normal procedure. received the message "uTorrent Install Wizard - We're sorry, the installer encountered an unrecoverable error and must quit. (Error: Permission denied: file: common.js; line: 10)" I'm currently running 45852 - thought I'd try updating to a beta - have normally been able to do this without issue. Tried again running the installer as admin. Went all the way through the process before telling me a newer version - 45918 - is installed and would I like to downgrade to 45852? Selecting 'No' loads 45918. Let's see how it goes. Note: this also added an extension - 'Safe Torrent Scanner' - to Google Chrome. There was no notification that this was going to happen.
  5. gjm

    3.5.x Beta

    @mike20021969 has done a lot of work on the solution, but I have seen some very negative feedback directed in that direction. As a user I consider this unfair; it has to be demoralising for the author/developer. Constructive criticism may be well. Attacks on credibility are not.
  6. gjm

    3.5.x Beta

    Trying to use http://download-new.utorrent.com/uuid/b8b31ca1-a8bc-447f-af78-dcf2d2d1e37b gets a new Window Defender message: PUA: Win32/Puasson.A!ml However, the date against it is an old one. 6/09/2020 12:51pm It is LAA related. C:\Users\...\uTorrent_LAA.exe Just seems odd that these LAA-related issues have only recently come up. Of course, that could just be Windows waking up to the existence of something
  7. gjm

    3.5.x Beta

    Can we just take a second and reflect - those developing this app are doing so for little, if any, reward. Coming on here and shouting the odds, complaining, whining and whinging is hardly encouraging. Constructive input with a full picture of situation is what is needed. Not cries of 'useless!' We're fortunate to have access to cutting edge developments. Support that, don't disparage it.
  8. gjm

    3.5.x Beta

    I've not seen Google block the LAA, but MS Windows certainly has. I've allowed it through Windows Defender (itself a bit of a mission) but it can keep reminding of a PUA unless further steps are taken.
  9. gjm

    3.5.x Beta

    My (rebuilt) laptop is making it very, very difficult to use this. Unwanted, potentially dangerous, blocked... Allow, allow, keep, keep, allow... And blocked. Keen to try it, but it's going to take some effort to persuade the laptop to let it through! (I understand what you've supplied, at a basic level, and why my laptop doesn't like it.)
  10. gjm

    3.5.x Beta

    I'm back on 45724 for the moment. I'll have another look at this later. Sunday working gets in the way!
  11. gjm

    3.5.x Beta

    Bare naked Windows 10, Build 19041.388 with the feature experience pack 120.2202.130.0. (Fully patched and up to date - trialing for a work deployment.) Notifications popped up as soon as I had installed from the magnet in mike's post above, and stopped as soon as I uninstalled.
  12. gjm

    3.5.x Beta

    Can't be 100% certain, but following install of 45768 Windows 10 immediately kicked up a fuss about wacapew.c ml having been installed. Unwanted or malicious software. Only way around this was to uninstall uTorrent (lending credence to it having been included in the build).
  13. gjm

    3.5.x Beta

    Magent was slow to start, but quick to complete. However... That bl**dy Adaware Web Companion POS is back. Wasn't in the last few updates - any reason why it has been included this time? There's no option to not install it, or notification that it is being installed.
  14. gjm

    3.5.x Beta

    There's some really weird stuff going on. Tonight, uTorrent has decided the default place to save a download is b\. Just that - no colon, nothing else. I don't even have a B: drive!
  15. gjm

    3.5.x Beta

    OK - this is weird. Running build 45628. Left it downloading one torrent (50-odd Gb) with several others in a 'stopped' state. Battery died at some point and the laptop shutdown - happened before, never a problem. Connected power, booted, started uTorrent, and.... Where are my torrents? They've gone. The one I had left downloading had completed, as it had been moved to my 'completed' directory. Nothing in the Recycle bin - deleting a torrent from uTorrent has always left something there. The missing .torrent torrent files are all in the C:\...\AppData\Roaming\uTorrent folder, including the one that had completed downloading. No actual loss as I'd not started the others - just set them up so I could do, later. No disk space issue - over 12Gb free space available. Curious. First time I've had any sort of issue with any build in a long time. Edit: Just dragged the .torrent files from the C:\...\AppData\Roaming\uTorrent folder to uTorrent, left them as 'stopped', shutdown uTorrent, restarted it, and... Yup - they're there. No problems. Restarting the added .torrents has led to a need to specify the destination folder name. That may be normal, of course. OK - fundamental problem. Downloading any new torrent with association to uTorrent, intended to start the torrent download, creates the 'Torrent error' "The system cannot find the path specified. (Write to disk.)" Looks like the new folder name is not being parsed, and an old folder named is being tried (and failing, when it has been removed.)