5.92 portable broken [download 5.91 from website]

[mogli]

For version 5.92 'CCleaner.exe'/'CCleaner64.exe' were moved to folders 'x86'/'x64'. However the folder 'lang' and the file 'portable.dat' were not moved accordingly. So the portable version is no longer portable and missing all languages except english. Please fix.

[mogli]

In other words the CCleaner executable can no longer find all needed files because they were moved to different folders without the necessary adjustments.

[lmacri]

Hi mogli:

I have no idea why the CCleaner.exe and CCleaner64.exe executables were moved into subfolders in v5.92 (rel. 11-Apr-2022), but I can confirm that if I unzip ccsetup592.zip and launch CCleaner64.exe from it's new location in the \x64  subfolder then I am unable to change the language at Options | Settings | Language.

If I enable  Options | Advanced | Save All Settings to INI File without making any other changes then ccleaner.ini will be save in that same \x64 subfolder.

 

If I cut and paste CCleaner64.exe back into it's correct location (i.e., in the main "root" directory where License.txt and portable.dat are located) then I am able to change the language and a new ccleaner.ini will be saved in the same directory as CCleaner64.exe.

-----------
64-bit Win 10 Pro v21H2 build 19044.1586 * Firefox v99.0.1 * Microsoft Defender v4.18.2203.5-1.1.19100.5 * Malwarebytes Premium v4.5.7.186-1.0.1645 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[bgavin]

This portable version hangs under Windows 10,0.19044.1706
It requires closing the process by Task Manager, as it won't close from a taskbar icon.
This is a Win10 problem, as the bug is not present in Win7.

The file structure of the ZIP has changed with this version.
I create a directory structure:  C:\Program Files\Portable\CCleaner for these files.
It hangs run from here under the Administrator account.

The failure is same when the zip is extracted to the local user profile, or from a network directory.
It creates an Event ID 1002 Task Cetegory (101).

All prior versions of Portable run correctly on this machine.
This new version, with the changed ZIP file structure is crashing.
 

[hazelnut]

Which build number of portable ? 

The new CCleaner 6 does not have a portable build, the one shown on the builds page is for 5.92 portable

https://www.ccleaner.com/ccleaner/builds

Also see here

https://community.ccleaner.com/topic/63001-ccleaner-609727-portable-not-available/#comment-336920

 

[bgavin]

I grabbed the portable zip, and expanded it to a drive.
In the x64 directory, I launched ccleaner64.exe

On the first launch, it displayed v 5.92
The file system dates are April 7. 2022 at 04:42am
The 64 bit version displays "v5.92.9652"

I closed it, and launched a second time.
This time, it asks several "do you want to run" questions.
When CC finally comes up, it is now v6.00.9727
Files are dated 5/11/2022 at 01:16 am.

Options | Keep Updated Automatically is checked.

 

Edited May 20, 2022 by bgavin
edited for clarity

[lmacri]

Hi bgavin:

Are you sure your automatic update didn't inadvertently run the installer for the "regular" version of CCleaner (e.g., ccsetup600.exe)?

I use CCleaner Free Portable v5.92.9652, and automatic updates are disabled at Options | Updates | Keep CCleaner Updated Automatically.  If I click the "Check for Updates" link in the bottom right corner of the interface it currently detects that a newer v6.00.9727 of CCleaner64.exe is available, but I know from past experience that if I click "Update Now" it will download unwanted files from the "regular" version of CCleaner that are not normally bundled with the ccsetupxx.zip file.  See nukecad's 14-Jan-2021 post in my thread How Do I Stop CCleaner Portable v5.76 From Automatically Checking for Updates?.

I've learned the hard way never to allow CCleaner Free Portable to update itself.  Instead I always unzip the latest ccsetupxxx.zip file from https://www.ccleaner.com/ccleaner/builds and then copy and paste the CCleaner64.exe and portable.dat files into the folder where I normally launch CCleaner Free Portable (currently a folder named D:\CCleaner on a removable USB thumb drive) to overwrite the old .exe and .dat files.  I use the default English interface and only keep four files in that D:\CCleaner folder.

-------------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.2 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[bgavin]

Yes, I am certain it did not run the regular version.
I do not have any CC installed in my list of installed software.

If it had run the regular installer, then v6 would be showing as an installed program.
It is not.

This is easy to duplicate.
Take a regular machine, or a VM, that does not have CC installed.
Download the portable zip, extract to any folder.
Run the CC x64 executable from the extracted files.
Note the version number.

Run the same x64 executable a 2nd time, note the file dates and version change.
Examine the installed programs in the Control Panel, you will not see a regular installed CC.

Note:  there is an architecture change in this version.
The previous portable ZIP had the EXE in the top folder.
The new portable zip, has the EXE in either the x86 or x64 folder, along with multiple new files.

I normally install the portable version into C:\ProgramFiles\Portable\CCleaner with a script.
The latest version failed, due to the changed files in the new portable directory structure.
Something changed in the new version.

Edited May 21, 2022 by bgavin
added addition data

[lmacri]

34 minutes ago, bgavin said:

Yes, I am certain it did not run the regular version.
I do not have any CC installed in my list of installed software.

If it had run the regular installer, then v6 would be showing as an installed program....

Hi bgavin:

Sorry, I realize my previous post might not have been clear.  If I click "Check for Updates" in the CCleaner Free Portable interface and choose "Update Now" it doesn't actually install the "regular" CCleaner Free program on my hard drive.  It just dumps files normally bundled inside the ccsetupxxx.exe installer (e.g., the Emergency Updater file CCUpdate.exe which is not normally included with the Portable version)  on the removable USB thumb drive where my CCleaner Free Portable files are located.

I'm sure I could update my CCleaner Free Portable v5.92.9652 to v6.00.9727 by downloading the "regular" ccsetup600.exe installer from https://www.ccleaner.com/ccleaner/builds, unpacking that self-extracting installer with 7-Zip and then copying the newer CCleaner64.exe v6.00.9727 executable to my removable USB thumb drive to replace the old CCleaner64.exe  v5.92.9652 executable.  However, I have no interest in using the new Performance Optimizer introduced in v6.00.9727 and prefer to wait until the developers at Piriform / Avast feel that they have CCleaner Portable  v6.0.x version that is functioning correctly and ready for wide release, per employee Dave CCleaner's 18-May-2022 post <here>.
-------------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.2 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[lmacri]

57 minutes ago, bgavin said:

Note:  there is an architecture change in this version.
The previous portable ZIP had the EXE in the top folder.
The new portable zip, has the EXE in either the x86 or x64 folder, along with multiple new files.

Hi bgavin:

The change in folder structure (i.e, where the 32-bit CCleaner.exe and 64-bit CCleaner64.exe excutables were moved out of the root folder and into separate \x86 and \x64 subfolders) started with CCleaner Portable v5.92 - see mogli's 11-Ap-2022 5.92 Portable Broken about problems this created for non-English users.  I suspect this is one of the issues that Piriform / Avast will have to fix before CCleaner Portable v6.0.x is ready for wide release.
-------------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.2 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[bgavin]

23 minutes ago, lmacri said:

Hi bgavin:

Sorry, I realize my previous post might not have been clear.  If I click "Check for Updates" in the CCleaner Free Portable interface and choose "Update Now" it doesn't actually install the "regular" CCleaner Free program on my hard drive.  It just dumps files normally bundled inside the ccsetupxxx.exe installer (e.g., the Emergency Updater file CCUpdate.exe which is not normally included with the Portable version)  on the removable USB thumb drive where my CCleaner Free Portable files are located.

 

Yep.
This is what it is doing.
Check for Updates is checked by default.
The first time an action is performed, such as a Clean, it updates to v6, brings in CCUpdate.exe and the others.

Q: is there a registry key, or ?? I can incorporate in my script to disable automatic update, and uncheck all the options to delete cookies?

The newer/newest CC is failing to display over remote access to a client's server, which is what prompted this bug report.
The latest Quickbooks Hub utility is also failing the same way, under the latest Win10 build.
I will have to chase this down further.

I save all the old CC portable versions, so it will be easy to downgrade a version or two to decide if this is version specific.
Or (more likely) yet another Windows 10 "feature".

[lmacri]

10 hours ago, bgavin said:

... This is what it is doing. Check for Updates is checked by default. The first time an action is performed, such as a Clean, it updates to v6, brings in CCUpdate.exe and the others..

Q: is there a registry key, or ?? ...

Hi bgavin:

See my thread How Do I Stop CCleaner Portable v5.76 From Automatically Checking for Updates? that I mentioned <above>, which includes images of the CCleaner Update task that was created in my Windows Task Scheduler when the Emergency Updater (CCUpdate.exe) was inadvertently added to my Portable build files.  There is an explanation in my original 14-Jan-214 post about why this Emergency Updater was added to the "regular" CCleaner v5.36 installer in 2017, but it made no sense for this scheduled CCleaner Update task to be running in the background for my Portable build when the required CCUpdate.exe executable was located on a removable USB drive (D:\ drive) that was rarely plugged in to my computer.  Here's an old image from my 2021 thread showing the scheduled CCleaner Update task repeatedly failing with an error (Last Run Result = 0x80070002) on my system because my USB thumb drive was unplugged and the task could not locate D:\Portable\CCleaner\CCUpdate.exe:

I believe I simply right-clicked the Cleaner Update task in Task Scheduler and chose Delete from the pop-up context menu (see the TenForums tutorial How to Delete Scheduled Task in Windows 10) but I'm guessing I might still still have some stray registry left behind in my Windows registry. You could try running the registry cleaner in CCleaner to look for stray registry entries related to Piriform or CCleaner (or use regedit and search for registry entries related to "Piriform" as ALF60 suggested on 14-May-2022 in the Norton Tech Outpost thread CCleaner v6.0.9727 Released 12-May-2022, Portable Build Delayed), but I would suggestion caution if you choose to do so.  I normally don't allow my CCleaner Portable build to make any connection to the backend Piriform / Avast servers (see my 21-Jan-2021 post in How Do I Stop CCleaner Portable v5.76 From Automatically Checking for Updates? about how I've created an outbound block in my Windows Firewall rules for CCleaner64.exe) but if you want to leave the CCleaner Portable settings at Options | Updates | Keep CCleaner Updated Automatically ENABLED or use any other feature in the CCleaner Portable interface that requires a connection to the backend Piriform / Avast servers then you might break that functionality.

The main crux of the problem is that Piriform / Avast's idea of a Portable build is to just take the identical 32-bit CCleaner.exe and 64-bit CCleaner64.exe files used with the "regular" installed version of CCleaner, bundle them in a ccsetupxxx.zip file with some language files and a portable.dat file to make it a portable build, and ensure that any configuration changes made in the interface are saved in a ccleaner.ini file.  What they really need to do is re-design CCleaner.exe and CCleaner64.exe files specifically for the portable build so that it can't create a scheduled Emergency Updater task or registry entries and doesn't include other unnecessary features like a Software Updater and Performance Optimizer that really don't belong in a portable program that can be run from a removable USB drive on multiple machines with different operating systems and different software/hardware configurations.

Quote

Q: is there a registry key, or ?? I can incorporate in my script to disable automatic update, and uncheck all the options to delete cookies?

I'm not sure what your script does, but the ccleaner.ini files will contain all the custom settings from your previous CCleaner Portable version.  As long as your script only overwrites the old 32-bit CCleaner.exe (if required), 64-bit CCleaner64.exe and portable.dat files (plus any required language files if you use a non-English interface)  and does not delete the old ccleaner.ini file or copy over any extraneous files like CCupdate.exe then there shouldn't be any need for your script to re-create the custom settings for your updated interface or perform other cleanup routines.  I personally prefer to always keep my CCleaner Portable files in the same folder (in my case, in a folder I created on my removable thumb drive at D:\Portable\CCleaner) so that the path to my CCleaner64.exe file never changes and I won't need to create a new ccleaner.ini file with all the default configuration settings the first time I launch the updated CCleaner64.exe executable that I manually copied and pasted into that folder.
-------------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v100.0.2 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1676 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[lmacri]

11 hours ago, bgavin said:

..... I save all the old CC portable versions, so it will be easy to downgrade a version or two to decide if this is version specific....

Hi bgavin:

Just an aside, but note that you should be able to download older CCleaner Portable .zip files by browsing to https: // download.ccleaner.com/portable/ccsetupxxx.zip. For example, if you ever need the .zip file for CCleaner Portable v5.76 browse to https://download.ccleaner.com/portable/ccsetup576.zip .

[bgavin]

Thanks for the pointer to the old files.
I normally keep all the prior versions in a ..\DOWNLEVEL directory on my main service drive.
Over the years, I have learned the hard way to do this... because so many downlevel versions are removed.

I install Portable into C:\Program Files\Portable\CCleaner on the client machine, then run from there.
This is a fixed location, so the INI files for that client are always current.

The parent directory name is compatible with both x86 and x64 architectures.
My script determines which platform CCxx.exe is required and installs it and it support files.
WinXP clients require the sunset version which is a separate source from the current Portable.

[nima]

I experienced the same as bgavin right now. Downloaded the zip file for portable version, unpacked it, started it. and whoosh it autoupdated to the 6something version despite the fact that I unchecked autoupdate in my old portable version.  Put the files of the install version into the folder of the portable version.  Not  good at all. Apart from this I encounter general problems in updating the portable version (extra post in te help request section). 

Oh , and both the portable and the install version are lacking any language except English.

[lmacri]

3 hours ago, nima said:

...Oh , and both the portable and the install version are lacking any language except English.

Hi nima:

Just an FYI that I was able to restore the non-English languages in CCleaner Free Portable v5.92 by moving the .exe executable (either CCleaner.exe from the \x86 subfolder and/or CCleaner64.exe from the \x64 subfolder) into the correct "root" folder where the portable.dat file and \lang subfolder are located.  See the images in my 13-Apr-2022 post in mogli's bug report at 5.92 Portable Broken.

If your .exe executables automatically upgraded from v5.92 to v6.00 after you unzipped the Portable ccsetup592.zip file (the version that is still available at https://www.ccleaner.com/ccleaner/builds as of 04-Jun-2022) then I suspect the same workaround would also allow you to switch to a non-English language in the v6.00 interface.
-----------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * Macrium Reflect Free v8.0.6758 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[bgavin]

So far, it appears the Portable is going to update itself if the update boxes are checked or not checked.

My process:
Clear the destination folder.
Unzip to the destination folder.
Check destination for update files, none found.
Launch CC portable.
Settings:  uncheck all update boxes
Run a CLEAN function.
I then notice version has changed to v6, and update files now in the destination directory.

Registry key:  HKEY_CURRENT_USER\Software\Piriform\CCleaner
UpdateCheck = 0
UpdateKey = SZ for date string

[Dave CCleaner]

@bgavin Having the Portable edition write preferences to the registry seems like a recipe for unintended consequences.  Have you got Options > Advanced Save all settings to INI file checked?  And, if so, what are the update settings in your CCleaner.ini? eg:

• UpdateBackground=1
• UpdateCheck=1
   

[bgavin]

.INI in the portable directory shows UpdateCheck=0

As to registry... nearly every programmer in the world fails to understand the true meaning of "uninstall", because they always leave registry droppings behind.
CCleaner is no exception, apparently.

A long time ago, I used to run the installed version, hence the registry entries.
When I moved to the Portable version, I *uninstalled* the installed version.
I did not check for registry droppings, of which there is a full load, similar to the portable INI file.

I can certainly delete the entire registry structure, as it appears to be tied to only a single key, as shown in my post above.

Found more registry entries:

HKEY_LOCAL_MACHINE\SOFTWARE\Piriform

Edited June 4, 2022 by bgavin

[lmacri]

3 hours ago, Dave CCleaner said:

Having the Portable edition write preferences to the registry seems like a recipe for unintended consequences....

Hi Dave CCleaner:

I've never had the v6.00 update pushed out to my CCleaner Free Portable v5.92 (unzipped on 13-Apr-2022 before CCleaner v6.00 was released on 12-May-2022) that I run from a removable USB thumb drive.  The ccleaner.ini file I'm using now was copied and pasted from my previous v5.91 portable and currently has:

UpdateBackground=0
UpdateCheck=0

Note that I was running a test for another user (see my 13-Apr-2022 post in mogli's 5.92 Portable Broken) and made the mistake of unzipping a fresh copy of ccsetup592.zip on my hard drive in C:\Users\<myusername>\Downloads and immediately double-clicking the CCleaner64.exe file now located the \x64 subfolder, which generated a brand new ccleaner.ini file with all the default settings.  As noted in mogli's thread, there is something seriously wrong with the structure of the folders and files in the ccsetp592.zip file and launching that CCleaner64.exe file appeared to create a scheduled CCleaner Update task in Task Scheduler that tries to run the emergency updater CCUpdate.exe, a file that normally isn't bundled with the Portable build. Note that I've deleted this scheduled CCleaner Update task since the image below was captured, as well as CCleanerDU.dll, CCleanerReactivator.dll and all the other unnecessary files and folders bundled inside ccsetup592.zip that aren't required to run the Portable version of CCleaner.

 

2 hours ago, bgavin said:

... As to registry... nearly every programmer in the world fails to understand the true meaning of "uninstall", because they always leave registry droppings behind.
CCleaner is no exception, apparently.

A long time ago, I used to run the installed version, hence the registry entries....

I've never installed the "regular" version of CCleaner Free on my Win 10 computer but when I searched my registry today for "Piriform" I found dozens of registry entries in HKEY_CURRENT_USER\SOFTWARE\Piriform\CCleaner, HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner and others.  I don't know when these registry entries were first created but I suspect most, if not all, were created when I launched CCIeaner64.exe during my 13-Apr-2022 test of CCleaner Free Portable v5.92 for mogli and created a new ccleaner.ini file (i.e., before I copied over my old v5.91 ccleaner.ini file with my customized settings and deleted all the other unnecessary files and folders bundled inside ccsetp592.zip that aren't required to run the Portable version of CCleaner).  Portable software should never be allowed to make these types of changes to the registry.  Here's just a partial list of what I found:

-----------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620

[bgavin]

Portable does indeed create registry entries.

HKEY_CURRENT_USER\Software\Piriform\CCleaner
HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner

I deleted both keys previously.
Then I ran Portable 5.92 with a Clean and Registry scan.
After doing so, both the above keys are again created.
42 values are created below as (Cfg)xxxx all are REG_SZ type.
These appear to be the same found in the portable INI.

 

[nima]

10 hours ago, lmacri said:

Hi nima:

Just an FYI that I was able to restore the non-English languages in CCleaner Free Portable v5.92 by moving the .exe executable (either CCleaner.exe from the \x86 subfolder and/or CCleaner64.exe from the \x64 subfolder) into the correct "root" folder where the portable.dat file and \lang subfolder are located.  See the images in my 13-Apr-2022 post in mogli's bug report at 5.92 Portable Broken.

THANKS, yes, this did the trick. Funny, I tried it the other way round, copying the ini from the old version into the 64 subfolder, but this didn't do the trick.

[Andavari]

On 04/06/2022 at 16:29, bgavin said:

Portable does indeed create registry entries.

HKEY_CURRENT_USER\Software\Piriform\CCleaner
HKEY_LOCAL_MACHINE\SOFTWARE\Piriform\CCleaner

Where you unzipped CCleaner Portable make sure the portable.dat file is in the same folder as CCleaner.exe and CCleaner64.exe, it's required so it knows to not create registry data.

----------------------------

If you don't have portable.dat in that folder:

1. Manually create it in Notepad by copying+pasting this into an empty Notepad window:
#PORTABLE#

2. In Notepad save to the folder where CCleaner.exe and CCleaner64.exe are located, it's required to use quotes around the file name so Notepad doesn't create a text document, save as example:
"C:\CCleaner Free Portable\portable.dat"

[bgavin]

Your suggestion above is the not directory structure in the ZIP file.

Unzipping to a parent directory, this top level directory holds the portable.dat file, and the child \x64, \x86 and \lang directories.
If one assumes to run either X86 or X64 from the unzipped structure, one has to assume the EXE will search for ..\ for portable.dat and the lang directory.

If the developer intended for the user to tweak the unzipped directory structure, I would be surprised.
As this would require the end user be smart enough to shift the directory structure around to something different than when it unzipped.

As a developer, I would be searching in the startup directory first, then ..\ for portable.dat and any required ..\lang files.
 

[lmacri]

2 hours ago, Andavari said:

Where you unzipped CCleaner Portable make sure the portable.dat file is in the same folder as CCleaner.exe and CCleaner64.exe, it's required so it knows to not create registry data...

Hi Andavari:

My image below shows the three other files [ccleaner.ini, portable.dat and License.txt (optional)] I normally keep in the same folder as my CCleaner64.exe executable.  I do not have a system with a 32-bit OS so I don't need the CCleaner.exe executable, and I use the English interface so I do not need the \lang subfolder in that same location.  Note that I only use the Custom Clean feature and don't want to use Health Check, Software Updater, Performance Optimizer, or any of the other bloat that's been added to recent versions of CCleaner.

As bgavin pointed out, unlike CCleaner Free Portable v5.91 and earlier versions, the unzipped ccsetup592.zip file no longer has the CCleaner64.exe and CCleaner.exe executables in the same "root" folder as portable.dat and License.txt.  Anyone using CCleaner Portable v5.92 who made the made the mistake of running the CCleaner64.exe file while it was still located inside the \x64 subfolder (which I did while running a test for mogli) now has all this garbage in their registry.  That's likely how I got the unwanted CCleaner Update task created in my Task Scheduler (shown in my first image <above>) as well.

Piriform / Avast really messed things up in v5.92 when they moved the executables out of the "root" directory where portable.dat and License.txt are still located , and this needs to be fixed before the next portable version is posted at https://www.ccleaner.com/ccleaner/builds.
-----------
64-bit Win 10 Pro v21H2 build 19044.1706 * Firefox v101.0.0 * Microsoft Defender v4.18.2203.5-1.1.19200.5 * Malwarebytes Premium v4.5.9.198-1.0.1689 * CCleaner Free Portable v5.92.9652
Dell Inspiron 15 5584, Intel i5-8265U CPU, 8 GB RAM, 256 GB Toshiba KBG40ZNS256G NVMe SSD, Intel UHD Graphics 620