Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


WalksInSilence

Member
  • Content Count

    21
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

8 Neutral

About WalksInSilence

Profile Information

  • OS
    Windows 7 x64
  • Country

Recent Profile Visitors

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

  1. Like others here, on my Win7 64bit machine I use FF v56 and even that is not perfect with certain legacy addons - at some point even before v56 the download manager: DownLoadThemAll which I've used for years the GUI stopped displaying as well as did with earlier versions but was still. OK. Classic Theme Restorer (obviously still very popular) is now shown as disabled and can't be launched from the Tools menu. I miss it a lot. Strangely Adblock Plus though shown as disabled is still working and although you can not use Favicon Customiser any more the new icons I had applied before it was disabled still work. DownloadThemAll displays OK and is usable in later FF versions than v56 but far from ideal and was the main reason I went back to v56 on that machine. What I use now, and kept up to date as an alternative is the portable addition of Waterfox, an excellent FF spin off. Although it still has the later FF like GUI display issues with DownLoadThemAll all the other extensions work pretty much as intended. At times I forget I'm not using FF.
  2. The next stage of 'recovery' is acceptance - that is just not going to happen.
  3. Hell that made me angry - I've been waiting, expecting a MS update to try to sneak install another unwanted telemetry gathering update for two years since the last one. I was suspicious too that originally was a hidden rather than a standalone optional update. Now we have the proof - MS are clearly ignoring the Customer Experience program opt out. I've usually waited before installing any monthly updates to allow anything like this to be reported and therefore avoided. The one time I do not wait and they sneak it in. Its easy enough to deal with, you just disable or delete the task using Control Panel > System and Security > Administrative Tools > Task Scheduler and find the cuckoo as described elsewhere here in: Task Scheduler Library > Microsoft > Windows > Application Experience. It showed this time as a "Compatibility Appraiser" task. The previous one was listed as an AitAgent (Application Impact Agent). I'll be watching more closely for it or something else to reappear from now on.
  4. The July updates I was offered and I installed yesterday were MS .NET Framework and Server update (KB4507004) and the Security update (KB4507449) plus the usual Malicious Software Removal Tool. In Installed Updates it shows three new entries: MS .NET Framework Update - KB4506997 , Security Update for Windows - KB4507449 and Update for Microsoft Windows - KB4507004. I'm assuming the latter was a combined package because it was only listed as three 'important' updates and that included the MSRT. I noted from the report that the unwanted telemetry gathering update if present creates a scheduled task. I checked and I do have such a task but it is Disabled and Never run. It is the one I disabled myself in June 2017 when they last tried to foist a telemetry gathering task on my system despite specifically opting out of the 'Customer Experience' program. I am glad this possibility of MS having tried to do that again as part of the July monthly roll out has been bought to my attention. I'll be watching that disabled scheduled task very closely and if it even twitches I'll hit it with big hammer. EDIT I don't bloody believe it. A scheduled MS Windows telemetry gathering task has literally just run as I checked back here for any replies.
  5. We had all this sort of stuff: dire warnings of instant infection by multiple unspecified security risks with Windows XP. IT magazines were running multiple articles for month's beforehand stoking up fear about what was going to happen and how your 'old' WinXP PC would suddenly become redundant and have to be put out to pasture like some senile OAP. The fact was/is WinXP remained and still remains usable online, with care. I was using it, protected by a good AV and other security software, for over 3 years after support ended. The only reason I stopped using it was because the 14 year old laptop it was on suddenly died (serious component failure - probably the dedicated GPU). It is generally only the other software, particularly browsers, being updated to include features/functions that WinXP did not support that was the problem. But old browser versions still worked and many other software creators supported WinXP long after MS dumped it, some still do. I expect the same will be true for Win7 as well.
  6. Thanks, information appreciated. Obviously you would not make changes to the registry without backing it up first so it could be reversed (can't think why in this case, but you might want to) so it would be useful to know where they end up or, if that is not how they work, what registry values they are actually altering.
  7. It is not clear to me so apologies for my ignorance or stupidity: if somebody wants to use those two registry files UCyborg has so helpfully provided provided as an alternative fix for this problem where, precisely, are they to be installed?
  8. Thanks for this additional information about these matters especially that in the first post which confirms that I was not going mad and/or my (Win7) OS was stuffed up. It was MS removing services without any warning yet again. I was perplexed by the fact one game: Tomb Raider 5 suddenly started provoking the behaviour described ie. very high CPU use and the process would continue even when the game was shut down. Reinstalling it did not work and I thought I must have just not noticed these problems when I first installed and played the game 18 months ago. A batch file fix I was pointed to via another forum provided in this blog worked perfectly for me and there have been no consequence since I ran it.
  9. I do not have that but there are several ways of getting Windows Explorer (Win7) to open in an elevated state if that is all you want to do. One is to create/use a customised shortcut so any .exe opens with elevated privileges. https://winaero.com/blog/open-any-program-as-administrator-without-uac-prompt/ That tells you how to do it but also provides a link to a tool for created elevated shortcuts automatically. Not used it myself so this is certainly not an endorsement. If you just search for how to create an elevated shortcut there are plenty of other articles on the same subject with similar information. I created and use such a shortcut to launch "cmd" in full elevated admin state which by default I found that, despite being the only user and admin on the PC concerned, I was not allowed to run System File Checker or Chkdsk. If I launched them using Run > cmd, the usual way of starting the Command line, it said I did not have the administrative permissions to do that. Instead I had to use an administrative 'trick': launching it instead by typing "cmd" it in the search box and then right clicking the search result: "cmd" and selecting Run as adminstrator. All just to be able to use these basic tools on my own PC. Creating an elevated permissions shortcut is a good alternative solution to that annoying problem if it is what you wanted the ElevatedExplorer.exe for.
  10. The main problem I have with AVAST for use in this case is its actual footprint. My reason for using MSE on a XP VM was because it was small, unobtrusive and did not conflict with anything else. My host OS is protected by a better AV but that has plenty of RAM and storage space available. My XP SP3 32bit VM does not. As it is the VM takes up 25GB+ of space on my primary drive, a smallish SSD, The last thing I want is AVAST using up the 800MB+ of space a typical, customised if not fully minimized, installation requires (main program files about 670MB + 111MB in ProgramData). You can use AVAST with MBAM (and incidentally Spybot too) and there is no conflict but you can not ignore that it is a beast of an AV and definitely slows down a PC. That is of great concern for me when using a XP VM with only 1GB of dedicated RAM. So whilst it is good to know AVAST still works with XP it is not anything like as unobtrusive as MSE; you will definitely notice the difference. I've used both on a XP SP3 32bit 1GB RAM laptop in the past ie. I replaced MSE with AVAST and even back then (7 years ago) the performance was affected very noticeably.
  11. Installed Panda Free AV on my XP VM and all so far so good. I still had to update MS .Net Framework 4 again as part of the install process to what appeared be described as an extended version (because of XP?) but once that was done it took less than 5 minutes to get it up and running. You do have to register an account but that is pretty standard for anything like this and there were a few opt outs that needed to be ticked during install but that's about it. Final Program Files folder size is under 120MB although there may be other normally 'hidden' Panda folders in AppData and ProgramData etc. The GUI is simple enough and although it includes totally unwanted info about how many files have or are being scanned and threats blocked I can live with that. I've just had it going on in the background for an hour or so today, longer than I use the VM normally anyway, and, as said, so far no unwanted 'extras' have appeared to blight the experience. Only thing I have noticed is that my XP VM takes a little more time than usual to both shutdown and restart but I am only using 1GB of dedicated RAM so I'm used to things taking considerably longer than on the host machine. So just to confirm, as long as MS .Net Framework is installed, and up to date, Panda Free works with XP 32bit SP3.
  12. Same here but I've found all the decent, small footprint anti-virus programs that report or are listed as still WinXP compatible require the most up to date MS .Net Framework 4 version to install. I wanted to keep everything as small as possible as it is a VM installation on a relatively small SSD primary drive. I tried Panda Free as it has had good-ish reviews and duly uninstalled MSE only to find that the installer would not work without an up to date MS .NET Framework 4 install as well. Worse: in uninstalling MSE, despite putting in a restore point beforehand I've found I've now lost what were the last AV definitions entirely and MSE went red showing my XP VM as unprotected and no way to get them back AKAIK. I do have other security products running including some measure of active protection but I've had to bite the bullet and install MS .NET Framework 4 on my XP VM just so I can install a new AV. I've not done that yet so do not know if the Panda installer will now work OK. There were about 20 updates required for MS .NET Framework 4 to get it all up to date and, surprisingly, once I got Windows Updates working on the XP VM and despite it having been updated with a what was supposed to be a comprehensive WinXP update disc, at install three years ago, there were even some other XP "important" updates to install as well. I'm going to leave it now for the day before trying to install another AV to replace MSE. I will be mighty peeved if after all the time spent trying to get this annoyance fixed has been wasted.
  13. Interesting and useful info to remember - makes sense too. The physical USB connection was probably detected and being disabled by the scanner itself because of the Wi-Fi link. But then the USB controller reconnects the device and you get into a continuous disconnection/re-connection loop.
  14. Can't help with interpreting that process monitor report but a bit of Googling came up with other users asking about what sounds like the same thing affecting both Vista and Win7. The reported cause identified was the: AuthenTec biometric fingerprint reader. Now, obviously, if you do not have that then this is not the cause for you but if you do it is a good bet it is. It seems the problem might be caused by a driver update so you could try rolling that back or failing that, and assuming you do not wish to use the device, the other solution suggested was just going into Device Manager and disabling it. Other causes of the same problem suggested were a faulty attached USB device of some sort or just the that plug it is not seated properly. So worth checking those too.
  15. A bit of a necro-post to add my own experience with Hibernate. I've tried all the solutions suggested as regards BIOS/UEFI, wake on LAN and power management settings but I'd regularly get my PC waking up from Hibernation apparently at random rather than when you used the keyboard. Except it was not random - I eventually found the culprit(s) were other electrical devices connected to my home's ring main. But it was not just any device or a device plugged in the same mains electricity socket or even in the same room. It was two particular TVs and either of their digital STBs. Nothing else I've tested has the same effect - not a microwave, powerful lamp, heater, hairdryer, hi-fi or anything drawing significant current, it is just those two TVs. Put the PC into Hibernation then turn on either TV/STB and it'll wake the PC nine times out of ten. But if I turn the TV/STB on before Hibernation there is no problem and if I turn the TV/STB off whilst it is in Hibernation, in the same circumstances, there is no problem either. It would seem that Hibernation maybe storing the electrical state of the system. There has to be a residual current being used to be able to wake the PC up from the USB keyboard. Turning the TV/STBs on must be being detected and treated as a keyboard stroke. But why only those two devices I can not begin to guess.
×
×
  • Create New...