Jump to content
IObit Forum
Top Free Driver Updater Tools Best 25 PC Optimization Software Best 22 Antimalware Best 22 Uninstaller Software IObit Coupons & Discount Offers PC Optimizer Mac Boost Advice IObit Coupons A Good Utility Program From IObit IObit Promo Codes IObit Coupon Codes IObit Coupons and Deals FAQs Driver Booster Pro Review

Buddahfan

Members
  • Posts

    639
  • Joined

  • Days Won

    2

Everything posted by Buddahfan

  1. Just upgraded to 17.2 and to my surprise the upgrade installed two iTop apps without giving me and option not to install them. They just showed up. Not wanting the apps, I used iObit Uninstaller to remove them, but a lot of directories and files were left over. Fortunately, I use an app called Everything Search so I was able to identify the left- over folders and files. Unfortunately, I couldn't delete them all from there and had to use File Explorer to hunt and peck to find the leftovers and delete them. But that wasn't all, after running ASC it said there were registry fragments left over, so I had to restart the computer. Lo and Behold on the restart the ASC startup optimizer app found one more iTop entry which it removed upon optimizing. This was not an experience that would lead me to recommending ASC to anyone.
  2. Normally I run Driver Booster Pro before I run ASC Pro. Today I did not and ASC recognized I needed to update some drivers on my device. That is good. The situation. While ASC recognized that some drivers needed to be updated, it gave me the error message "Drivers need to be updated manually" So I ran Driver Booster Pro and it found two drivers that needed to be updated. Driver Booster Pro successfully updated the two drivers I reran ASC and this time it didn't show that any drivers that needed to be update. The suggested improvement ASC should recognize that Driver Booster Pro is on the device and instead of saying "Drivers need to be updated manually" it should say "Run Driver Booster Pro"
  3. I l❤️ this product, but its updates are a real pain. Like two in two days, yuk Driver Booster really needs to be put in the Microsoft Store even it means getting rid of the PUPs. Surely, there are other ways IObit can think of to make money from this product.
  4. Firefox has just been updated to version 91.0 I noticed that it has disabled IObit Surfing Protection due to "Security and stability issues" See picture It was disabled on July 13th (see picture) and as of yet can not be re-enabled Why was it blocked? This add-on violates Mozilla's Add-on Policies. This add-on violates Mozilla's add-on policies by collecting ancillary user data.
  5. It's been a long time since I posted here. Anyway, I thought I would give the SysInfo program/app a try I like the it. I have some comments 1. Create a floating widget of the four temperature items with the option to minimize it. This would make it real time without having to take up so much display space. 2. Under Operating System replace IE with Edge. Many Windows users probably don't even know that IE still comes packaged with W10 and its updates. 3. Under Displays show multiple display info, like you do with Drives if applicable. I use two displays on my desktop devices and only the main one shows 4. Under Network show the users IP address and Router info, at least the name and model of the router 5. Add a category "Software" Show the user's default programs as indicated by Windows That is it for now. I like the program but it definitely needs some improvements😊
  6. There are two design flaws are in the "Startup Optimiztion" section. 1. Items recommended for removal from Startup are not given the option to ignore like in Driver Booster. Being able to ignore items recommended for Startup removal should then clear the tool from showing up in the "Startup Optimization" scan results As it is now the tool continues to show after a scan and the user has to click on it to see what is recommended for removal from Startup. This is an unnecessary waste of time each time a scan is run and can be eliminated by adding an "Ignore" button next to the item recommended for removal from Startup if the user so chooses.to ignore the item. This would then remove the tool each time a scan is run if there are no items recommended for removal from Startup that the user has not told ASC to ignore. If the user later decides to have the item removed from Startup they could then "Unignore" it as in Driver Booster. 2. When an item is recommended for removal from Startup and the user clicks the box to remove the item from Startup it "should not" disappear from the Startup Tab in the W10 Task Manager but be changed to "Disable" as if the user had directly disabled the item from running at Startup in the Task Manager. Making this change should then allow the user to open the W10 Task Manager and re-enable the item in Startup if they so choose. As it is now the user has to reinstall the program to get it to again show up in the notification area of the Taskbar. Like #1 above the way it works now is a waste of the users time in this case if they change their mind to allow the item to run at Startup after having chosen to not do so via ASC. Disclaimer. This analysis ws performed on W10 build 19008 and not W10 1903 the current RTM version of W10. Thanks for reading.:-)
  7. @Cicely I decided to lighten the load on my desktop computers by removing a number of apps for which Microsoft has an app with the same functionality. One of the apps I removed from my desktops was Smart Defrag. I removed several apps on all of my desktops to 1. improve the performance including the startup times 2. reduce the time I spend updating apps which has become a bit of a load now that I have six computers running Windows 10. Amazingly enough I am using all six of them. I decided to use Tweak-SSD for my Lenovos. It works good. Has improved the performance of both Lenovos and the price was right. Again nothing really against Smart Defrag. I had actually gone back to v 4.x before deciding to remove Smart Defrag all-together. I even removed CCleaner along with several other apps and just use Bitdefender Total Security One Click Optimizer and W10 Clean Mgr to clean up things on the my desktops when I am done. Still using Driver Booster on all six of my computers (I have two licenses) and of course IMF 4.0 RC Pro on my Lenovos
  8. Tried V 5.0 Beta. Went back to 4.X. Too many bugs in 5.0 Beta 1. Major one being that the graph does not show correctly. Showed 3.0% fragmented while 4.X right afterwards showed only 0.1% defragmented. Maybe 4.X has not worked correctly? I would hope not. 2. Defrag and optimize takes forever even though I have used 4.X to optimize and ran it just a few days ago. Even when I immeidately reran optimize it took forever. Lot of work to be with 5.0 Beta Suggest pulling it from public beta download sites until it becomes usable. More internal testing by IObit personnel needed before it becomes a viable public beta. Sorry that is how I see it.
  9. I am on the Windows 10 Insider Fasttrack Ring on one of my computers. This AM DB 3 Beta 2 Pro said I needed five updates. Three updates worked. The two that did not were Microsoft Visual Basic gaming component drivers. Since they are Microsoft drivers aznd the computer is on W10 unreleased build 10525 and I don't do gaming (sorry about that LOL). I just put them on ignore for now. Hopefully I will remember to take them off ignore when the next version of Windows 10 is released which I understand on't be until Nov at the earliest for those using Windows 10 Pro which I am. Cheers and logging off for now.
  10. Cicely: Regarding the Dell Wireless issue I just sent off the info you requested above.
  11. I don't like the idea of disabling my anti-virus software to download and install a driver update. This is what DB says. I think disabling AV software to allow a driver to update is foolish at best. This issue needs to be resolved by IObit. If my AV software blocks a a driver update I will go with the AV software everytime and then go from there with regards to a possible FP.
  12. DB 3 Beta Pro 2 v3.0.2.94 not catching a Dell wireless driver update. I was having problems with the wireless driver. I did a scan with DB 3 Beta 2 Pro and it said all drivers were up to date. I checked Windows 10 Device Manager and it said my wireless driver was 10.0.0.315 dated 5/11/15. I went to the Dell driver download website and it said the latest wireless driver for the computer was 10.0.0.318 dated 5/15/15. I downloaded and installed the driver. So far no problems but it did require a reset of my TV. I rescanned with DB 3 Beta 2 and indicated the correct wireless driver number.
  13. Cicely: I wish I could help further on this. Unfortunately over the weekend that computer running W10 crashed and and as a result I lost access to the Start Page and everything reachable by it. So I did a new install of Windows 10 on that computer which of course removes whatever helpful infomration might have been there. That information is now lost. If I see the situation with Driver Booster again I will try to remember to follow your suggestion.
  14. Windows 10 DB v3 Beta 2 Free version. I noticed this morning after a Windows 10 reboot that DB popped up after the reboot and told me I had drivers to update and to activate now which means to purchase a license. I have a license for DB but it is for only three computers and I chose not to buy an additional license for this computer so it is using the free version. Anyway I closed the popup and opened DB I did a scan and it said that I had no updates. Recommendation. Do not show this popup as a stand alone without showing the drivers that need to be updated after a scan. Ratjher if IObit does't want the free version to update all the drivers in the free version then show all the drivers that need to be updated after a scan is run but say "Activate to download and install: next to those drivers. P.S. Those same drivers showed up on the paid version but ironically the update failed.so I put them on ignore. The drivers are gaming drivers, Microsoft Visual C++ 2012 Redistributable (x64). As I recall there were three or four of them.
  15. Sorry for the long delay. In anycase I can not do as you request since I no longer have the Windows 8.1 tablet which is where the problem occurred.
  16. I was a bit premature on the driver updates to my Dragon Touch 8". it turns out that the driver update to the Intel SST Audio Device (WDM) driver killed the audio. Below are the details. Driver that DB 3.0 Beta Installed Intel SST Audio Device (WDM) Date: 11/7/2014 This resulted in loss of sound Dragon Touch Details CPU: Intel Atom Z3735F Bay Trail-T HWiNFO64 - Says Audio - Unknown or None From Windows Device Mgr Sound, video and game controllers Intel SST Audio Devices (WDM) Driver Provider - Intel Driver Date - 9/1/2014 (About two months before the date on the driver that DB 3.0 Beta installed) Driver Version: 603.9600.2801.48116 Digital Signer: Microsoft Windows Hardware Compatibility Provider Realtek I25 Audio Code - The driver for this updated without a problem I checked the Windows Event log and there were no error messages I was able to use DB 3.0 Beta to roll back the driver to the one from 9/1/2014 and the sound returned. I then told DB to igmore driver updates for this device.
  17. Just bought a Dragon Touch 8" Windows 8.1 tablet. Installed DB 3.0 Beta. It found 17 outdated drivers and updated them all without a problem.
  18. Installed Date: I did a clean install of Windows 10 TP 10162 on my Intel Haswell i5 4460. DB found two drivers to update. One from Intel and from Realtek. My question is why do a lot of the drivers from Microsoft in the list have an installed date of 21 June 2006? Clearly if I just installed 10162 a few days ago the drivers could not have been installed nine years ago For example the driver ACPI Thermal Zone version 10.0.10162.0 by Microsoft is showing and install date of 21 June 2006. I have attached a picture comparing the infomration in Driver Booster vs the driver information shown in NirSoft Driver View. Maybe the date column should be changed from Installed Date to "Driver Date" or there should be two columns, one for Driver Date and one for Installed Date.
  19. Since the vote is so close I suggest offering the user both options. They could choose one during the installation process.
  20. Just so people know. Reboots are often necessary to complete an update to the Windows OS to an app or to a driver. Often these updates which require a reboot are security fixes to the Windows OS. app or driver. Until the reboot is completed the security fix update may not be fully applied. Sometimes these security updates fix a "zero-day" vulnerablility. People who do not reboot their computer ASAP after recommended by Windows an app or a driver may be putting their computer at unnecessary risk to malware attack. Worse than that they may be putting themselves at risk of privacy invasion and possibly ID theft . They could even be at risk for financial loss if their computer becomes subject to a Ransomeware attack because they did not finish a security update by rebooting when instructed but waiting until it suits them.. To minimize risk to their computer and/or themselves a person should always reboot their computer ASAP after it is recommended by Windows, an app or a driver. Only rebooting when one chooses or it suit them not only could put the computer or the individual at risk but could even put their loved ones at risk if the loved ones have information on the computer in question. Now it could be that some members here are smart enough to know whether every update applied to their computer fixes a security risk and therefore only reboot when it suits them. I am not one of them and I have a feeling that the majority of computer users are like me in this regard. Therefore I highly recommend that people reboot when instructed by the computer and not when it suits them. P.S. In case people are wondering some drivers are OS unique. Some drivers may be backward compatible from say W8.1 to W7-SP1 or to XP (highly unliikey with XP) but a lot of drivers are unique to the Windows OS. What is often the case is that a new dirver version for an app comes to support the newest Windows OS. However, that is not always the case and sometimes drivers are uniquie to the OS despite what some may think or say.
  21. Thanks for the reply. I understand. One thing you could do is thorugh a Customer Experience option is collect a history of those drivers that have required an update for each Windows OS. I would think the reboot requirement is based upon a combination of the driver and Windows OS and not the driver version. Once IObit has has collected a database sufficiently large of the reboot history for each driver then they could note it as "probably requires a reboot" Once set up to collect the data I would think maintaining it and compiling it would take little effort. As I originally noted I think it would be helpful information for users to have In fact IObit could collect compile a percentage of reboot number for each driver and Windows OS combination and enter it into Driver Booster. For example. "An update to this driver on your OS requires a reboot in 95% of the time" You could enter everything but the percentage in a header and then put the percentage next to the driver..
  22. I am already using Bitdefender AV. So will turning on the Btidefender AV feature in IMF cause a problem? In anycase there would probably be no advantage to turning it on in IMF if I am already using Btidefender AV products. Dirfferent products depending on the Windows OS.
  23. Working good on W7-SP1 and W8.1. I like the fact that the Beta installs in a seperate folder from 2.X. This way I was able to compare drivers found by both. No doubt that 3.0 Beta is finding drivers that 2.X did not. So far no problems with 3.0 Beta on any of the computers I have it installed on. One suggestion. If possible I would like to see "requires restart/reboot" next to a driver that needs to be updated rather than having to wait for the new driver to install. This way a user could update drivers not requiring a reboot while they are using their computer and save the ones that require a reboot for a convienent time when they are not using their computer.
  24. Note: I had a sumilar problem with W8.1 but never reported it because as I recall there was no information supplied when the process failed OS: W10TP 10049 Smart Defrag 4.0.2.690 Computer uses UEFI to boot Wireless Keyboard: Logitech MK 320 Driver: Provider Microsoft Driver Date 6/21/2006 Driver Version: 10.0.10049.0 Digital Signature Microsoft Windows Situation: Attempting to do a Boot Defrag. All three boxes are checked. 1. Defragment Page files and Hiberation files, 2. Defragment MFT, 3.Defragament system files I get the following error message: UEFI failed on initializing keyboard, process will not continue Boot defragment is then skipped and the computer goes directly to login. There is no problem performing the boot defragment on two W10TP 10049 computers using BIOS rather than UEFI and a Logitech keyboard either the MK320 or MK260. I had a similar situation when I was running W8.1 on all three computers. The two booting under BIOS performed the boot defragment without a problem The one booting under UEFI as I recall succeeded performing two of the three processes. Sorry I can't remember which one failed. As I stated above I do not recall seeing a detaled error message. Just that that part of the Boot Defragment failed.
×
×
  • Create New...