[Smart Driver Updater Crack Full Keys With License Serial Key

0 views
Skip to first unread message

Betty Neyhart

unread,
Jun 13, 2024, 1:00:39 AM6/13/24
to pumcampmatu

i tried to enter "intelligent privsioning" by pressing "f10"-key: this brings me to a screen where i can choose between "self update" and "fallback". fallback seems to be a bootloader entry that tries to boot a linux kernel that ends up after 1.1seconds in a kernel panic as it was not able to mount root filesystem and "self update" boots a working linux kernel that tries to install a gaius.3.50-100.x86_64.rpm. i assume it therefore needs network connectivity so i connected (the first) ethernet port to a standard "home-network (dhcp), nat" but it stalls keep saying it installs that rpm file (has been running for days without changing any status).

HPE, first. please provide a better web portal that clearly describes which downloadable files (bios, intelligent provisioning, ...) should be used in order to update the system (have a look at supermicro.com how this could be achieved). and btw, please speed up your webservers....

Smart Driver Updater Crack Full Keys With License Serial Key


Downloadhttps://t.co/heobrRVMLL



HPE, please provide driver downloads for customers that do not want to relay on your propritary "intelligent provisioning" (that breaks) in order to still enable classic installs (just by inserting dvd/usb and running a clean install)

HPE, please provide more status and esp. progress ouput if you try to download files programatically by your setup scripts. running a download without asking for network connectivity and then trying to downloading a file that is about half gigabyte in size without displaying progress is sooo 1990. we're in 2021 now.

HPE, first, i ordered this server w/o iLO 5 enable pci express card, as it was hard to me (even if we do servers since 1995) to fire out that iLO won't work without this card, so i assumed iLO will work (but will not have a dedicated ethernet port, so shared among others). it's even possible to configure network (ip, subnet, gateway, ...) within iLO bios config but .... the configuration gets lost without a single note that you have to buy that enabler pci express card. HPE, it took me half a day to figure out that it's not that buggy as "intelligent provisioning" but you want me to pay $100 extra to persist my network config within iLO. you can have $200 if you disable iLO option within bios saying "put some more money in to get this feature activated"

HPE, never ever again a microserver. it's my 4th in the last decade and its still pain/ass. why can't you go slimmer? why "intelligent provisioning"? i'd like to run a raid setup within ncurses-like mode, no embedded web-browser that tries to hide some htpp://localhost services.

I've tried to update firmware via Intelligent Provisioning. The progress bar was stuck at 20% for 20-30 minutes, just saying "Downloading", and suddenly finished and asked me to reboot. Now I've rebooted, and got the same options as you "Self update" or "Fallback". I chose "Self update", and now I'm waiting for "gaius-3.50-100.x86_64.rpm to install, but I have no progress bar.

i had expected to quickly install a native version of windows server 2019, as this is the current server os from microsoft but without having a usable version of "intelligent provisioning" one has to run a classic install but cannot use smart array features as raid1, which sucks, of course.

i lost about half a day trying to set an ilo ip address which is actually possible but then looses it's configuration after reboot. after playing some hours i figured out that one has to buy that ilo enabler pci express card, which is totally ok so it's ok to spend some more money to get ilo remote console BUT its totaly inacceptable to provide configuration options to users and tell the users "config saved, please reboot" (or similar) and then do not persist configuration. i spent hours to figure out that this is a (anti) "feature", not a bug.

nevertheless, i resolved that issue today: as linux-only user i created the usb key from the "media recovery usb key" with gnu dd, which actually boots and shows progress bar: so i assumed the stick was created correctly but i then figured out that hpe has it's own tool for creating usb keys from iso files: it's called "hp usb key utility". i could not find a single hint one has to use that tool in order to create that usb key, even it's not mentioned in the download notes.

HPE, please FIX YOUR TOOLS. provide linux tools to create usb key. provide better descriptions in your downloads, provide scripts that work: display progress, display what's goin' on, diplay success or error messages. recovering "intelligent provisioning" does not result in an error or success message: your recovery script just reboots after completing.

after days of trouble i ask myself what's so hard in providing a slim, fast (static?) website that just holds .bin (bios, raid controller, ...) firmware/bios files that can be put on fatXX based usb keys and read by legacy bios or even uefi setups? why would one have to boot a linux kernel to open up a browser that communicates with ilo to configure a raid1 drive? for me it seems that HPE addresses "hobbyists" who "need" support in installing a operating system: i'd like to stay with vendors that allow me vanilla installations of o/s and provide device drivers to provide hardware support: i dislike broken tools that prevent installing o/s or patch files in install media just to speedup o/s installation which is not true for most of the o/s i use. never ever had to use days to setup a plain windows server on a raid1 array.

I downloaded and installed the new Norton Driver Updater yesterday and all the updates seemed fine with the exception for the update of the PCI Express Root Complex driver, which essentially got stuck in the "waiting" mode (see screenshot) and have stayed stuck ever since.

Subsequent research on my part has led me to believe that I may actually be better off not updating PCI Express Root Complex as many have had PC performance problems after the update. For this reason, I don't want to update this driver but I don't know how I should interpret the "waiting" mode (which stays on after rebooting the PC), and more importantly how to simply undo the attempted update.

If you click on the right arrow ">" next to the word "waiting" the little black disc gives the options to either skip the update or ignore the driver - use this to remove the "waiting" state and cancel the update.

CCleaner has the same issue and I wonder why this has started happening only in the last few days. For what it's worth Microsoft community users say that it is best not to update drivers on the recommendation of a driver updater.

My conclusion is that Norton Driver Updater was released to soon. In technical terms, this is a piece of junk. It created other PC problems and I regret installing it in the first place. I have now uninstalled the Driver Updater. Stay away from it, is my recommendation.

Totally agree mate, Norton are dodgy releasing a beta product as a fully fledged product without any mention of the risks involved. At least if you install a beta product you know you're potentially going to have issues and YOU make that decision, not like in this situation, we've gone in blind, trusting that the product is safe, only for a bunch of us to find that that is not the case, in my case it bricked my PC.

I am really sorry for all troubles associated with usage of our product. This is not intentional behavior.

In order to be able to help you I would like to ask you to send us your log files executing our Support Tool utility.

My problem is on my wife's computer, ASUS T100, and the Updater has jammed the whole system - the screen has a 'You have 1 outdated driver' image that I cannot remove - the cursor is not visible - and the touch screen is no longer working! When I try to restart the whole system, the computer simply goes back to the same place and nothing works! How do I get rid of the program and get back to being able to operate the computer at all? Frustrating!

Hi David,

Read the post from Uli a couple above yours, he's a Norton employee and trying to help, but as far as I know they haven't resolved any of the issues plaguing this dodgy programme. He's been looking into the same issue as yours on my laptop after the programme bricked my desktop and I had to reinstall Windows. Surprise, surprise, the Support Tool programme doesn't work properly either so you'll have to email the logs directly to him. Good luck, you're going to need it.

Hi GM Burgess255,

Not sure if you're replying to me or not but in my case Safe Mode couldn't fix the problem. It's not my first rodeo and I've resolved many issues over the PC years but not this one. I even paid for the Norton Help Desk people to remotely help but they couldn't fix it either, leaving me with a fresh installation as the only option. On my Laptop it's still running fine, it just has the waiting error mentioned by several others and there's no way I'm going to let the thing loose to make more changes and my laptop. I'm still waiting to hear back from Uli about that one. Thanks for trying to help.

I am really sorry for all troubles associated with usage of our product. This is not intentional behavior.
In order to be able to help you I would like to ask you to send us your log files executing our Support Tool utility.

Lugar52, best bet is to uninstall the bloody thing mate, it bricked my desktop and Norton want me to run the dodgy programme on it again to help them troubleshoot what went wrong - in your dreams, no way in the world !! It also gave me the waiting error on my laptop but at lest I haven't had to reinstall Windows on that one, but I certainly won't be letting the wretched programme loose on it that's for sure.

Pedroski, thank you, did delete the app which killed the waiting scenario; however, I did a reinstall with the idea to run and set the PCI Express Root Complex into the ignore state but it looks like Norton beat me to it.

Thanks for all comments! My problem was on my wife's computer and the program ended up stopping anything from happening - no cursor, no touch screen, not able to stop the program even re-booting etc. I eventually managed to get some access by using the keys and tabbing etc - a painful process! I've now deleted the driver update program and had to update the my Windows etc - but still trying to get to a usable computer!

795a8134c1
Reply all
Reply to author
Forward
0 new messages