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?
Download Zip https://oyndr.com/2yMfa9
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.
(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 no longer have Wise Care 365 installed. But, as I recall, it didn't have a Fast scan mode. It only had Default, Safe and Custom modes. I believe I tried both Default and Safe modes and they were pretty much the same ... LONG.
On the standalone Wise Registry Cleaner 9.38, the Fast scan took the aforementioned 13 seconds. The Deep scan took 20 seconds. They all check all the categories. I agree that the ActiveX category is the most time-consuming of all the categories. But, even then, the standalone Wise Registry Cleaner 9.38 takes only 7 seconds with the ActiveX category. This while Wise Care 365 takes several eternities with the ActiveX category.
For example, I installed Glary Utilities Portable 5.69 on that same day. And neither its Glary Tracks Eraser nor its Glary Disk Cleaner take remotely ANYWHERE near 4 minutes. Neither did my old Glary Utilities Portable 2.56. And neither does JetClean.
I didn't get around to checking much of any of the other functions in Wise Care 365. I was quickly turned off by the fact that the Registry Cleaner function, which I use often and regularly, was obviously seriously flawed. I immediately figured, "With this major Pterodactyl in the Oinment, I'm not gonna be adding Wise Care 365 to my Flash Drive arsenal of tools. So, I cut my exploration session way short.
i took screens to show you how i did a similar test and everything was fine. Then right as i was about to pat myself on the back for a job.......somewhat done i hit a key and an hour's worth of work was gone. I stewed until i ran wise today.....it hung on the scan, my pc was slow and boot was long. In short i was now experiencing similar issues. If the developer wants a true bug report it's this thread.
i was fortunate to be able to duplicate the issue. The trigger was using the reg defrag.......after that it all went to hell and my pc acted the same as chim. since i knew what caused it i simply used the restore function and im 100% back to normal. I'm not entirely comfortable calling this a bug......we are using Xp which could entail several versions and service packs, the other programs that work fine don't indicate anything really but any program could be causing a conflict, I think the reason restore/backup warnings appear b4 we use these features are because messing with the registry is like making small talk with a skitzoid....it doesnt take much to put em out of whack and it can go very south very quick.
Great to see you dropping by to report and chime in on this problem with Wise Care 365, Cloaker. The more users that pop in and mention their similar problems, the more evidence there is and the more theoretical likelihood that the Wise Devs will look into this.
Well, I see it this way. The Glary Disk Cleaner and Glary Tracks Eraser within Glary Utilities 5.69 that I installed just the other day function EXACTLY as and take the SAME amount of time to scan as the standalone versions of those 2 apps. Therefore, I see no reason why the Wise Registry Cleaner within Wise Care 365 shouldn't function EXACTLY as and take the SAME amount of time to scan as the standalone version of Wise Registry Cleaner.
Otherwise, what use is it? The idea is to with Wise Care 365 have a one stop, all tool maintenance bonanza within ONE app. The way it stands right now, it'd be a case of something like --- oh, most of its tools are fine ... just don't use the Registry Cleaner and the Registry Defrag. It wouldn't be that desired ONE app treasure chest.
"The Glary Disk Cleaner and Glary Tracks Eraser within Glary Utilities 5.69 that I installed just the other day function EXACTLY as and take the SAME amount of time to scan as the standalone versions of those 2 apps. Therefore, I see no reason why the Wise Registry Cleaner within Wise Care 365 shouldn't function EXACTLY as and take the SAME amount of time to scan as the standalone version of Wise Registry Cleaner."
essentially your using common sense based on your observations and that is why your convinced this is a detail worth noting- it may end up that way but 999 times out of 1000 , in the world of code , you have to replace common sense with variables, flow, pc logic and over all experience to improve the troubleshooting accuracy.
These all in ones are tough because everything needs to flow efficiently allowing easy navigation without conflicts between modules. The code is different between the 2 brands, the gui, the routines and clock cycles it takes to run....there are so many variables. The only way you can expect the same out of wise is if it was the same code- they scan and work totally different where as glary seems to be just calling the routines and creating the impression they are integrated. this prob hasnt happened in 2 years so i will keep an eye on the next release.
For me the question is what does wise modify as part of its defrag routine in xp? something is conflicting from within the gui AFTER the process runs or a residual affect is created but im not sure we will get much on this with Xp being the focus. There will be a point they will have to end support for it and these are the instances that lead too it. We'll see right
I know Wise and Glarysoft don't use the same code and the same Devs. But, no matter how it gets reasoned and explained away ... inferior functionality shouldn't be excused / given a pass simply for the convenience of being part of an All In One package. No matter how the functions get executed / carried out behind the scenes by ANY of this type of apps, bottom line, no ands, ifs or buts, the Registry Cleaner function within Wise Care 365 takes a mega LONG time vs ANY of this type of app be it All In One or standalone.
I use CCleaner, Glary Disk Cleaner, Glary Tracks Eraser, Glary Utilities, JetClean, Wise Disk Cleaner, Wise Registry Cleaner and even some of the tools within Revo Uninstaller. And NONE of those take anywhere remotely close to 4 minutes to accomplish any of their scanning functions. They all take seconds.
What the reason is for the mega LONG scanning time with Wise Care 365's Registry Cleaner function, I have no idea. The bottom line reality is that it exists. And I sure hope that they do fix the issue so that I can use Wise Care 365. Cuz I do like and use some of the other great Wise products like Wise Disk Cleaner, Wise Registry Cleaner, Wise Program Uninstaller and Wise Video Downloader.
I've never tried a Registry Defragger, be it a Wise product or any other app. Defragging the Registry makes me wayyy too leery of disaster. If I were to FUBAR my computer into a non-booting status all because of too much curiosity with defragging the Registry, that would be it. My computer would be toast. I don't have the System Recovery / Windows Reinstall CD for it. So I just leave that area of maintenance alone.
Yeah, I unfortunately concur that at some point almost assuredly, Wise will also end support for Windows XP with their products. Pretty much all software developers are headed in that direction in one timeframe or another.
The thing was whether, as is the case with any software product when an issue is discussed on that product's forum ... there was the unknown of whether the Devs had already seen this thread and / or already knew about the issue. A lot of times on various forums, we're left to wonder whether our feedback was ever even seen.
Oh, it wasn't an optical illusion. You did confirm it before. I actually meant to write, "Thanks for confirming that AGAIN, Xilo" at the beginning of my previous comment. It just got away from me.
7fc3f7cf58