HP Z440’s Bricked Hard
-
No, not cool. You never want a vendor image.
@JaredBusch So this bootable only included raid drivers for windows to see the partitions it seems. I was able to see the partitions and delete them to install new OS from my Win10 DVD. After Windows booted there was an HP installer on that disk as well, but I just skipped running it as I assumed it was just bloatware. When you say vendor image, in this instance, what could be different besides the bloatware part? Are we talking outdated RAID drivers or default drivers used by Windows, and wouldn't those drivers update as soon as you ran an obligatory "Check for Updates"?
Trying to be better and you guys are really helping, so I appreciate the input.
-
@G-I-Jones said in HP Z440’s Bricked Hard:
No, not cool. You never want a vendor image.
So this bootable only included raid drivers for windows to see the partitions it seems. I was able to see the partitions and delete them to install new OS from my Win10 DVD. After Windows booted there was an HP installer on that disk as well, but I just skipped running it as I assumed it was just bloatware. When you say vendor image, in this instance, what could be different besides the bloatware part? Are we talking outdated RAID drivers or default drivers used by Windows, and wouldn't those drivers update as soon as you ran an obligatory "Check for Updates"?
Trying to be better and you guys are really helping, so I appreciate the input.
I really don't follow your explanation. You've managed to boot into Windows to see and HP installer? where did this Windows boot environment come from? I mean I know it's possible to create a bootable windows environment, like you can for Linux, though it's use is pretty rare - and MS recently killed the ability to make this in 1903 I think.
A vendor image, is normally an enhanced/changed/updated version of the standard Windows install ISO. It's updated by the vendor to include drivers (often needed to boot/install/see the storage) and other vendor related junkware, and sometimes third party crap.
Most of use around here avoid using vendor images because of the second and third things listed there, but that does sometimes leave us in a pickle. By this I mean - we have to make our own image that includes the storage drivers so the image will boot and be able to detect the storage devices automatically and allow a typical installation.
There are google'able instructions on how to do this - warning - it is a HUGE PITA! You have to normally update at least two areas of the image to make it work - one for for the boot portion and one for the gui portion, I think I've read there is a third place sometimes - but it's been a while, so I could be mistaken.
Instead of updating the image - others in the thread have already suggested that you put the drivers onto a USB stick and provide it to the system during the storage selection process - there will be a button for add drivers, upon adding the drivers, the system should then see the storage device and allow you to act upon it.
-
@G-I-Jones said in HP Z440’s Bricked Hard:
Are we talking outdated RAID drivers or default drivers used by Windows, and wouldn't those drivers update as soon as you ran an obligatory "Check for Updates"?
Maybe, maybe not, If HP hasn't give them to MS to certify, then no, Windows Update won't have them, and you'd have to update them manually.
MS can update all kinds of drivers, but, most manufacturers don't provide the drivers to MS (I'm assuming MS charges them for this) so you, the user, have to acquire the new software (BIOS/UEFI/Drivers, etc) and install them yourself.
-
I really don't follow your explanation. You've managed to boot into Windows to see and HP installer? where did this Windows boot environment come from?
@Dashrender - I was able to install Windows from a Microsoft ISO that I had, as my initial issue was seeing the partitions, this bootable (HP gave me) gave me the necessary drivers to do such. After Windows was installed, I was then able to open the same bootable USB (HP gave me) and there was a HP Installer included. I opted not to run it because the likelihood of it being bloatware.
A vendor image, is normally an enhanced/changed/updated version of the standard Windows install ISO. It's updated by the vendor to include drivers (often needed to boot/install/see the storage) and other vendor related junkware, and sometimes third party crap.
Most of use around here avoid using vendor images because of the second and third things listed there, but that does sometimes leave us in a pickle.
Appreciated.
-
@Dashrender said in HP Z440’s Bricked Hard:
By this I mean - we have to make our own image that includes the storage drivers so the image will boot and be able to detect the storage devices automatically and allow a typical installation.
This is overthinking things. You Boot to the Windows ISO and then simply click "Load driver" and have the driver on another USB.
No one in the SMB should be doing anything else. Building bootable images with all the right drivers? waste of time. You should not be installing often enough to worry about that.
-
@JaredBusch said in HP Z440’s Bricked Hard:
@Dashrender said in HP Z440’s Bricked Hard:
By this I mean - we have to make our own image that includes the storage drivers so the image will boot and be able to detect the storage devices automatically and allow a typical installation.
This is overthinking things. You Boot to the Windows ISO and then simply click "Load driver" and have the driver on another USB.
No one in the SMB should be doing anything else. Building bootable images with all the right drivers? waste of time. You should not be installing often enough to worry about that.
You're not wrong - but I was trying to give the OP all the information.
