Chim

So what's the deal with Wise Care 365?  Does it by any chance require, only work on very fast and powerful computers?  Is there a minimum Processor that a computer must have in order for Wise Care 365 to work properly?
 
Last year when I first tried Wise Care 365, it was on my old Dell GX280 Small Form Factor with only a Pentium 4 processor and either 1 or 2 Gig of RAM running Windows XP Home SP3.  As I recall, as soon as I would try the Registry Cleaner function, my GX280's CPU fan would quickly start spinning at top speed, sounding like a helicopter.  And the scanning would immediately go into a snail's pace crawl to the point that I would quickly have to abort.  Yet, the standalone Wise Registry Cleaner (PortableApps.com version) would scan quickly, without a problem and without remotely making my GX280 break a sweat.
 
Now that I have a Dell Optiplex 780 with an Intel Core 2 Duo processor with 4 Gig of RAM running Windows XP Pro SP3, the other day I again decided to give Wise Care 365 another shot.  This computer being a much more powerful and quieter computer, the CPU fan does not go into top speed helicopter mode when running a scan with the Registry Cleaner function.  But, the scan does take a noticeably, undeniably LONG time at 4 minutes and 35 seconds!  That while the standalone Wise Registry Cleaner took all of 13 seconds ... and found the SAME 41 items that it took Wise Care 365's Registry Cleaner function 4 minutes and 35 seconds to find.    
 
So what's going on?
(1)  Is Wise Care 365 not meant for older, weak Pentium era computers with Windows XP?
 
(2)  Why does the Wise Care 365 Registry Cleaner function take wayyy longer to complete a scan vs. the standalone Wise Registry Cleaner ... while finding the same amount of items?  From what I see, I'm tempted to reason that maybe it's that the Wise Care 365 Registry Cleaner function is wayyy more thorough than the standalone Wise Registry Cleaner ... even though ultimately the same amount of items are found by both.  Because it's not like the Wise Care 365 Registry Cleaner function is scanning at a crawl on my Dell Optiplex 780.  No.  I see that it's actually scanning very speedily.  It appears to be checking a lot of something.  Unless it's an optical illusion, I'm tempted to think that the Wise Care 365 Registry Cleaner function scans a ton more Registry Entries than the standalone Wise Registry Cleaner.  I just keep going back to that in the end, ultimately both apps find the same amount of items.  Odd.      

So what's the deal with Wise Care 365?  Does it by any chance require, only work on very fast and powerful computers?  Is there a minimum Processor that a computer must have in order for Wise Care 365 to work properly?
 
Last year when I first tried Wise Care 365, it was on my old Dell GX280 Small Form Factor with only a Pentium 4 processor and either 1 or 2 Gig of RAM running Windows XP Home SP3.  As I recall, as soon as I would try the Registry Cleaner function, my GX280's CPU fan would quickly start spinning at top speed, sounding like a helicopter.  And the scanning would immediately go into a snail's pace crawl to the point that I would quickly have to abort.  Yet, the standalone Wise Registry Cleaner (PortableApps.com version) would scan quickly, without a problem and without remotely making my GX280 break a sweat.
 
Now that I have a Dell Optiplex 780 with an Intel Core 2 Duo processor with 4 Gig of RAM running Windows XP Pro SP3, the other day I again decided to give Wise Care 365 another shot.  This computer being a much more powerful and quieter computer, the CPU fan does not go into top speed helicopter mode when running a scan with the Registry Cleaner function.  But, the scan does take a noticeably, undeniably LONG time at 4 minutes and 35 seconds!  That while the standalone Wise Registry Cleaner took all of 13 seconds ... and found the SAME 41 items that it took Wise Care 365's Registry Cleaner function 4 minutes and 35 seconds to find.    
 
So what's going on?
(1)  Is Wise Care 365 not meant for older, weak Pentium era computers with Windows XP?
 
(2)  Why does the Wise Care 365 Registry Cleaner function take wayyy longer to complete a scan vs. the standalone Wise Registry Cleaner ... while finding the same amount of items?  From what I see, I'm tempted to reason that maybe it's that the Wise Care 365 Registry Cleaner function is wayyy more thorough than the standalone Wise Registry Cleaner ... even though ultimately the same amount of items are found by both.  Because it's not like the Wise Care 365 Registry Cleaner function is scanning at a crawl on my Dell Optiplex 780.  No.  I see that it's actually scanning very speedily.  It appears to be checking a lot of something.  Unless it's an optical illusion, I'm tempted to think that the Wise Care 365 Registry Cleaner function scans a ton more Registry Entries than the standalone Wise Registry Cleaner.  I just keep going back to that in the end, ultimately both apps find the same amount of items.  Odd.      

So what's the deal with Wise Care 365?  Does it by any chance require, only work on very fast and powerful computers?  Is there a minimum Processor that a computer must have in order for Wise Care 365 to work properly?
 
Last year when I first tried Wise Care 365, it was on my old Dell GX280 Small Form Factor with only a Pentium 4 processor and either 1 or 2 Gig of RAM running Windows XP Home SP3.  As I recall, as soon as I would try the Registry Cleaner function, my GX280's CPU fan would quickly start spinning at top speed, sounding like a helicopter.  And the scanning would immediately go into a snail's pace crawl to the point that I would quickly have to abort.  Yet, the standalone Wise Registry Cleaner (PortableApps.com version) would scan quickly, without a problem and without remotely making my GX280 break a sweat.
 
Now that I have a Dell Optiplex 780 with an Intel Core 2 Duo processor with 4 Gig of RAM running Windows XP Pro SP3, the other day I again decided to give Wise Care 365 another shot.  This computer being a much more powerful and quieter computer, the CPU fan does not go into top speed helicopter mode when running a scan with the Registry Cleaner function.  But, the scan does take a noticeably, undeniably LONG time at 4 minutes and 35 seconds!  That while the standalone Wise Registry Cleaner took all of 13 seconds ... and found the SAME 41 items that it took Wise Care 365's Registry Cleaner function 4 minutes and 35 seconds to find.    
 
So what's going on?
(1)  Is Wise Care 365 not meant for older, weak Pentium era computers with Windows XP?
 
(2)  Why does the Wise Care 365 Registry Cleaner function take wayyy longer to complete a scan vs. the standalone Wise Registry Cleaner ... while finding the same amount of items?  From what I see, I'm tempted to reason that maybe it's that the Wise Care 365 Registry Cleaner function is wayyy more thorough than the standalone Wise Registry Cleaner ... even though ultimately the same amount of items are found by both.  Because it's not like the Wise Care 365 Registry Cleaner function is scanning at a crawl on my Dell Optiplex 780.  No.  I see that it's actually scanning very speedily.  It appears to be checking a lot of something.  Unless it's an optical illusion, I'm tempted to think that the Wise Care 365 Registry Cleaner function scans a ton more Registry Entries than the standalone Wise Registry Cleaner.  I just keep going back to that in the end, ultimately both apps find the same amount of items.  Odd.      

Since yesterday March 23rd, I see on Major Geeks that there is supposedly already a WRC 9.42.613 version out.  However, at the Wise Download Center, the latest WRC version out is 9.41.
 
Is the Wise Download Center behind or is Major Geeks wrong?

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I'm almost sure that I have put in this request before and obviously it fell into an abyss of it didn't happen.
 
Okay, here goes Take II ... this time with a screen capture for illustration.
 
As you can see in the attached screen cap, all the rest of the apps in my PortableApps.com platform menu are real nicely titled to where one knows at a glance what exactly they are. THEN you see down there at 2nd from the bottom outlined in the red box where it says "WiseCleaner.com." What the ....? That certainly doesn't specify at a glance remotely what the app is.
 
Well, it happens to be Wise Registry Cleaner. WHY not have it specify exactly what it is just like all the other apps? That's all I'm asking. Just a simple request to have the menu title display "Wise Registry Cleaner" or "Wise Registry Cleaner Portable." That would be extremely helpful and greatly appreciated.

I'm almost sure that I have put in this request before and obviously it fell into an abyss of it didn't happen.
 
Okay, here goes Take II ... this time with a screen capture for illustration.
 
As you can see in the attached screen cap, all the rest of the apps in my PortableApps.com platform menu are real nicely titled to where one knows at a glance what exactly they are. THEN you see down there at 2nd from the bottom outlined in the red box where it says "WiseCleaner.com." What the ....? That certainly doesn't specify at a glance remotely what the app is.
 
Well, it happens to be Wise Registry Cleaner. WHY not have it specify exactly what it is just like all the other apps? That's all I'm asking. Just a simple request to have the menu title display "Wise Registry Cleaner" or "Wise Registry Cleaner Portable." That would be extremely helpful and greatly appreciated.

The other day I decided to try the Program Uninstaller in the Utilities Sidebar over on the right of WC 365.  I figured if it worked exactly as the standalone version, I'd naturally delete the standalone version from my PA.com platform in my Flash Drive as I would of course no longer need it.  No use having the same app twice in my Flash Drive apps arsenal.
 
Well, if I deciphered correctly what then happened ... I believe Program Uninstaller proceeded to be downloaded.  I aborted the download because [A]  I already have a Wise Program Uninstaller.    I have Dial Up Internet and didn't expect to be downloading anything at that time.
 
QUESTION #1:  Do ALL of those "NEW" utilities in the Utilities Sidebar need to first be downloaded before being able to be used?
 
QUESTION #2:  Will these "NEW" utilities eventually be incorporated into Wise Care 365 in a future version?  If so, how many versions from the current version?  One?  Two?  You know ... so they wouldn't have to first be downloaded and installed.
 
In other words, I'm hoping to get to the point to where Wise Care 365 covers ALL the bases and functions of ALL the current Wise standalone products that I use.  I like to operate lean & mean.  So the less standalone Wise apps that I'd have to have installed in my PA.com platform and have WC 365 cover all those functions ... the better.  Especially given that right now I haven't even seen a portable version of Wise Force Deleter.

I'm almost sure that I have put in this request before and obviously it fell into an abyss of it didn't happen.
 
Okay, here goes Take II ... this time with a screen capture for illustration.
 
As you can see in the attached screen cap, all the rest of the apps in my PortableApps.com platform menu are real nicely titled to where one knows at a glance what exactly they are. THEN you see down there at 2nd from the bottom outlined in the red box where it says "WiseCleaner.com." What the ....? That certainly doesn't specify at a glance remotely what the app is.
 
Well, it happens to be Wise Registry Cleaner. WHY not have it specify exactly what it is just like all the other apps? That's all I'm asking. Just a simple request to have the menu title display "Wise Registry Cleaner" or "Wise Registry Cleaner Portable." That would be extremely helpful and greatly appreciated.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

The other day I decided to try the Program Uninstaller in the Utilities Sidebar over on the right of WC 365.  I figured if it worked exactly as the standalone version, I'd naturally delete the standalone version from my PA.com platform in my Flash Drive as I would of course no longer need it.  No use having the same app twice in my Flash Drive apps arsenal.
 
Well, if I deciphered correctly what then happened ... I believe Program Uninstaller proceeded to be downloaded.  I aborted the download because [A]  I already have a Wise Program Uninstaller.    I have Dial Up Internet and didn't expect to be downloading anything at that time.
 
QUESTION #1:  Do ALL of those "NEW" utilities in the Utilities Sidebar need to first be downloaded before being able to be used?
 
QUESTION #2:  Will these "NEW" utilities eventually be incorporated into Wise Care 365 in a future version?  If so, how many versions from the current version?  One?  Two?  You know ... so they wouldn't have to first be downloaded and installed.
 
In other words, I'm hoping to get to the point to where Wise Care 365 covers ALL the bases and functions of ALL the current Wise standalone products that I use.  I like to operate lean & mean.  So the less standalone Wise apps that I'd have to have installed in my PA.com platform and have WC 365 cover all those functions ... the better.  Especially given that right now I haven't even seen a portable version of Wise Force Deleter.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

So what's the deal with Wise Care 365?  Does it by any chance require, only work on very fast and powerful computers?  Is there a minimum Processor that a computer must have in order for Wise Care 365 to work properly?
 
Last year when I first tried Wise Care 365, it was on my old Dell GX280 Small Form Factor with only a Pentium 4 processor and either 1 or 2 Gig of RAM running Windows XP Home SP3.  As I recall, as soon as I would try the Registry Cleaner function, my GX280's CPU fan would quickly start spinning at top speed, sounding like a helicopter.  And the scanning would immediately go into a snail's pace crawl to the point that I would quickly have to abort.  Yet, the standalone Wise Registry Cleaner (PortableApps.com version) would scan quickly, without a problem and without remotely making my GX280 break a sweat.
 
Now that I have a Dell Optiplex 780 with an Intel Core 2 Duo processor with 4 Gig of RAM running Windows XP Pro SP3, the other day I again decided to give Wise Care 365 another shot.  This computer being a much more powerful and quieter computer, the CPU fan does not go into top speed helicopter mode when running a scan with the Registry Cleaner function.  But, the scan does take a noticeably, undeniably LONG time at 4 minutes and 35 seconds!  That while the standalone Wise Registry Cleaner took all of 13 seconds ... and found the SAME 41 items that it took Wise Care 365's Registry Cleaner function 4 minutes and 35 seconds to find.    
 
So what's going on?
(1)  Is Wise Care 365 not meant for older, weak Pentium era computers with Windows XP?
 
(2)  Why does the Wise Care 365 Registry Cleaner function take wayyy longer to complete a scan vs. the standalone Wise Registry Cleaner ... while finding the same amount of items?  From what I see, I'm tempted to reason that maybe it's that the Wise Care 365 Registry Cleaner function is wayyy more thorough than the standalone Wise Registry Cleaner ... even though ultimately the same amount of items are found by both.  Because it's not like the Wise Care 365 Registry Cleaner function is scanning at a crawl on my Dell Optiplex 780.  No.  I see that it's actually scanning very speedily.  It appears to be checking a lot of something.  Unless it's an optical illusion, I'm tempted to think that the Wise Care 365 Registry Cleaner function scans a ton more Registry Entries than the standalone Wise Registry Cleaner.  I just keep going back to that in the end, ultimately both apps find the same amount of items.  Odd.      

I don't know if it's just on my side, but I've been noticing some problems with the functionality of the forums.
 
(1) If I try to post a reply in a thread via the "Reply to this topic" box at the bottom of the thread ... nothing happens. The reply doesn't remotely attempt to get posted. I end up having to use the Black "Reply to this topic" BUTTON at the upper right of the page.
 
(2) The next issue: Well, I was planning on attaching a screen capture image to show the problem that I'm encountering, but the problem is that I'm not being allowed to attach an image because the problem IS right at that area. So, I'll try to explain the problem.
 
Right there at the "Attach Files" area at the bottom left of the reply box ... where the "Choose Files" BUTTON is --- some other text that appears to read "uldn't load plug" is being superimposed on the Choose Files BUTTON. This is rendering the Choose Files BUTTON non-functional.
 
In case it helps zero in on the problem --- I am using Windows XP Pro SP3. I am using the latest version of avast Free Anti-Virus. I am using NetZero Dial Up Internet.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.

I mentioned this issue over on my Wise Care 365 vs. Wise Registry Cleaner thread.  I thought I'd put it here in its own thread since on the surface, it looks like it MIGHT be a WDC issue instead of a Wise Care 365 issue ... although I could be wrong.  Either way, now I have visual proof and more detail.
 
In the 2nd image attached below, you'll notice how Wise Care 365 4.5.6 managed to detect 695 Junk Files Created by Applications for a total of 92.3 MegaBytes.  While it found various items first in that category ... starting with the yellow highlighted items, it was predominantly a mountain of Maxthon Cloud browser cache.  Of course, I only included a micro sample of that Maxthon cache.  
 
In the 1st image attached below, you'll notice how Wise Disk Cleaner 9.41 detected NO Junk Files.  That is quite a huge discrepancy.  I could be wrong in my thinking, but I would think that WDC and the Common Cleaner function in Wise Care 365 would / should work pretty much the same and yield same results or at least pretty close to the same.
 
True, as was mentioned in the Wise Care 365 vs. Wise Registry Cleaner thread, Wise does NOT at this time support Maxthon.  However, logically, the results of this experiment seem to indicate that either WDC or the Common Cleaner function in Wise Care 365 is wrong ... or both --- and needs to be fixed to match the other app.  In other words, either Wise Care 365 should NOT have detected all those 695 items as Junk Files Created by Applications ... or WDC SHOULD have detected them instead of missing them.
 
Oh, and also, as can be seen in the 2 images, there also seems to be a noticeable discrepancy in the Old Prefetch Data between the 2 apps.  True, it's not a huge discrepancy as with the other issue, but a discrepancy nonetheless.  I don't know if there is a logical explanation for that or whether that also needs to be looked into.
 
Sorry about how I discussed the 2nd image first instead of starting with the 1st image.  It's that after submitting my topic, the order of my images was mysteriously swapped.  So, I had to edit the text to match the order of the images.