Jump to content

Andavari

Moderators
  • Posts

    22,343
  • Joined

Posts posted by Andavari

  1. Good that it's just the "old" bug that also existed on XP. XP always had a peculiarity when running ChkDsk stating it was correcting the volume bitmap for whatever reason due to some erroneous error that was never patched. I do know on old XP that running Disk Cleanup with the Recycle Bin box ticked and if there's something for it to remove from the Recycle Bin will cause ChkDsk to fix some erroneous error that Windows 10 never finds, for example on a USB external/portable drive formatted with NTFS. Something similiar happens on XP after Volume Shadow Copy ("VSS") service in used for instance by Tweaking.com Registry Backup - afterwards the internal drive with the largest amount of free space all of a sudden has some erroneous error that ChkDsk will repair.

    Maybe time for Microsoft to come up with a new file system because NTFS is very old anyways with some limitations, or they should overhaul it and remove the bugs.

    USN journal bug/misery:
    Another NTFS quirk is if the USN journal is enabled on for instance USB external/portable backup drives (HDD or SSD), it makes it extremely difficult or impossible to use Safely Remove on those drives in a timely manner which has the potential of corrupting files on the drives as most people will get fed up waiting a long time and just unplug the USB cord. Manually disabling USN journal on those drives makes it possible to Safely Remove them almost instantly. I recently reported such a bug to Microsoft within the last two weeks because something in Win10 was consistently enabling and re-enabling USN journal on USB external/portable drives that were NTFS formatted, it got fixed within 2 or 3 days, and I suspect it was perhaps tied to something Windows Defender was doing because allot of antivirus' trigger enabling USN journal on internal drives just not usually USB drives.

  2. Probably spammed because the old hardware is still valid for retro gaming systems for playing games without emulation, and can still be bought as new old stock or even brand new production from certain China websites.

  3. Reverting registry changes using backup .REG files isn't always successful and simply restarting the computer can make them useless especially with things like even slight hardware changes that happen.

    Windows 10 back in April 2018 turned off the making of automatic registry backups, I manually re-enabled it because who knows if/when it could save me a bunch of headaches. Here's how to manually re-enable it (note that it's probably considered a power-user or advanced method since it details manually editing the registry itself):
    https://www.techrepublic.com/article/how-to-turn-on-automatic-registry-file-backup-in-windows-10/

  4. Some computer manufacturers have YouTube videos on how to fix it, such as Dell. It's rather common and there's many YouTube videos showing how to potentially fix it.

    YouTube Search:
    https://www.youtube.com/results?search_query=hard+disk+at+100+percent+usage

    Edit:
    One solution would cost a little money, and that is to install an SSD (at least 240GB to 256GB) as the main boot drive Windows is installed on. Then re-purpose and use that HDD as mass storage for games, music, video, etc. Even if the CPU isn't modern installing an SSD as the boot drive is the most significant upgrade where the results are immediately noticed.

  5. Disk Cleanup was the first thing I ran before I posted about WinSxS, it didn't do anything. Neither did using that Task Scheduler command in the link you provided, and that's as far as I'll go and I'll leave well enough alone because messing with the WinSxS folder is like opening a can of worms.

  6. I searched the registry but that's not really a problem, I only removed one reference to it.

    This is what caught my eye in the WinSxS folder:

    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1_none_fdfd5401e6c802a9\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1_none_fdfd5401e6c802a9\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1_none_fdfd5401e6c802a9\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1_none_fdfd5401e6c802a9\FlashUtil_ActiveX.exe
    
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_815470a5fb446c4e\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_815470a5fb446c4e\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_815470a5fb446c4e\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.172_none_815470a5fb446c4e\FlashUtil_ActiveX.exe
    
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.356_none_816e1571fb309416\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.356_none_816e1571fb309416\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.356_none_816e1571fb309416\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.356_none_816e1571fb309416\FlashUtil_ActiveX.exe
    
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.656_none_816e1b23fb308b8b\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.656_none_816e1b23fb308b8b\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.656_none_816e1b23fb308b8b\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.656_none_816e1b23fb308b8b\FlashUtil_ActiveX.exe
    
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.901_none_819f2efffb0c7898\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.901_none_819f2efffb0c7898\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.901_none_819f2efffb0c7898\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.901_none_819f2efffb0c7898\FlashUtil_ActiveX.exe
    
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1140_none_3952653acc5f8b3e\activex.vch
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1140_none_3952653acc5f8b3e\Flash.ocx
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1140_none_3952653acc5f8b3e\FlashUtil_ActiveX.dll
    C:\Windows\WinSxS\amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.18362.1140_none_3952653acc5f8b3e\FlashUtil_ActiveX.exe

     

  7. Whatever that Microsoft "update" (let's call it a remover instead) does it leaves Flash Player intact on the system.

    May not be able to use it anymore, but I would've thought they'd nuke it off the system. Running the Adobe Flash Player Uninstaller doesn't get rid of the leftover of it either.

    The only thing I can see that's happened invisibly in the background when running that Microsoft remover was it removed the Control Panel icon for Flash Player settings, and made the .SWF extension useless.

  8. Stopping a defrag doesn't destroy data since all defrag software is using the Microsoft Defrag API in the background which is relatively safe.

    You state the built-in Windows Disk Optimizer won't let you defrag the drive, that's just the GUI interface that stops you from defragmenting certain file systems or drive types (such as it won't let you defrag a USB Flash Drive), whereas via an admin Command Prompt you can use the command line defrag regardless of disk type or file system that's supported by Windows, I use it all the time.

    Here's a search for "Windows 10 Command Line Defrag":
    https://duckduckgo.com/?t=ffab&q=windows+10+command+line+defrag

  9. 10 hours ago, jagman said:

    WE are a "throw-away" society caused by Capitalism and greed that runs amuck.

     

    Yes here in the U.S.A. that is indeed true.

    There's a different throw-away aspect and that's how much trash is just littered across the country, if there's a store around that sells food items (dollar store, gas station, or grocery) near a neighborhood people seem to think the ground and peoples land/yards are for their trash. In my city it has gotten out of control, it didn't look so trashy 15 years ago when there wasn't as much littering. I'm so fed up with it because my house is near a dollar store and a grocery store. If I was in the government making laws I'd try to make the fines for littering obnoxiously expensive; first offense $2500, second offense $5000, third offense $10000, fourth offense $20000 including prison time.

  10. 70-ish GB of fragments taking that long is way too long in my opinion, it should've finished a few hours later after you started it.

    48 hours is beyond my level of patience and I would've cancelled it after getting past the 12 hour mark myself (although I would never subject my backup drive to that much time of "defragging"). That plus it's allot of time for the HDD and if it's a backup drive with your important backups stored on it you might want to consider cancelling the defrag and use something else that will finish ages quicker like the Optimize Drives feature built into Windows 10.

    If it's an USB 3.0 External HDD be aware those can be very slow with a lack of performance after a particular Windows 10 update disabled write cache on them - but that's likely only helpful to have write cache enabled when writing to them.

    One thing I've seen on Windows 10 is some USB 3.0 External HDDs take forever to defrag, i.e.; it seems impossible because of how slow they defrag. Plugging those drives into an old PC with only USB 2.0 and Windows XP finishes ages quicker - odd but true.

  11. On 09/12/2020 at 10:20, siliconman01 said:

    I don't know about y'all, but every time I open folder C:\Program Files\CCleaner on any of my systems, I find multiple *.dmp files laying around.  I added the code below to my Custom.ini file; however, it could/should be added to winapp2.ini in my opinion.

    
    [CCleaner DMP Files *]
    LangSecRef=3024
    Detect=HKCU\Software\Piriform\CCleaner
    FileKey1=%ProgramFiles%\CCleaner|*.dmp

     

    Could just put it into 'Options > Include'. There's a number of programs I've did that for over the years, but never bothered making a winapp2.ini entry for them since .dmp would literally be the only thing getting cleaned.

  12. The UAC "autorun" added into Task Scheduler is there so Windows doesn't always prompt/warn when launching CCleaner and prompting if it's ok to start it. It's easy to disable in CCleaner itself by going into: Options > Advanced

    As for not liking software connecting to the web and subsequently annoying you in the process there's the Windows Firewall to block access, and the Windows HOSTS file to block addresses.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.