• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Any failures related to Hotkey UWP service? Click here for tips.
Common problems for Battery
We would like to share some of the most frequently asked questions about: Battery Reports, Hold a charge, Test and Calibrating Battery . Check out this link: Is your notebook plugged in and not charging?
HP Recommended
EliteBook
Microsoft Windows 10 (64-bit)

Despite the release notes, the latest version of HP Image Assistant does not work with the latest version of Windows 10 (release 1909) when I try to run it I get the following message: "HP Image Assistant does not support Windows 10 version 1909 for this platform. Would you like to download the list of supported platforms and operating systems?" The downloaded list does not include version 1909 despite the release note that says it does.

23 REPLIES 23
HP Recommended

@erichalter 

 

Well, Rats.  Looks like this is indeed the case.

 

I ran a couple of tests to confirm,

and

I have reported the problem.

 

Hang in there.

 

Update / Edits

Still waiting, although we have now garnered the attention of those who will investigate the cause and provide a solution.

 

For those reading:

Tested on Windows V1903 - then updated to Version 1909 and HPIA does not detect updates for this latest version of Windows. 

 

HPIA_V1909_Search_1HPIA_V1909_Search_1

 

Personal Observation:  Assuming the software has indeed be updated to support V1909, this may be simply a catalog error.  Still bad, of course, but perhaps more easily repaired.

 

 

Thank you for participating in the HP Community Forum.

We are a world community of HP enthusiasts dedicated to supporting HP technology.

Click Thumbs Up on a post to say Thank You!

Answered? Select the relevant post "Accept as Solution" to help others find it.

 

 

Dragon-Fur

HP Recommended

I wanted to add my experiences with version 4.2.4.1 and Windows 1909:

I updated my HP ProBook 450 G6 with the latest 1909, downloaded  SP99899 and installed it.

 

I have had mixed results running version 4.2.4.1 on Windows 1909.

Sometimes it runs normally and will analyze the system. (It has successfully completed the indicated driver updates as well.)

However, sometimes when I click on the Analyze button, it reports the version of Windows is not supported by the program.

I have experienced this inconsistant behavior several times but have not been able to determine a pattern for when it will or will not run normally.

HP Recommended

@jr246 

 

Thanks for your comments.

 

Yes, I have seen the same result(s) and have passed these on to those in HP who can look at it.

 

Consistent inconsistency - one of my least favorite types of errors.  Rats.

 

Thank you for participating in the HP Community Forum.

We are a world community of HP enthusiasts dedicated to supporting HP technology.

Click Thumbs Up on a post to say Thank You!

Answered? Select the relevant post "Accept as Solution" to help others find it.

 

 

Dragon-Fur

HP Recommended

Try again and see the reference images for your platform are now available.  I just tested on an 840 G5 running 1909 and HPIA worked properly.

 

There has been an effort to get 1909 reference images loaded to the HP Support Site.

 

Joel

I am an HP Employee.

If you like my post, click the thumbs up.
HP Recommended

Tested on 850 G3 running 1909 and failed

HP Recommended

Hi all,

 

I saw the same issue about 3 weeks back, and have not tried 1909 again because it is a time sink to do so if it still has not been fixed. This is the only thread I have found that speaks to this problem specifically, I am subscribed to this thread and will keep googling on it as I deploy more machines.

 

I am at the initial stage of deploying 26 HP Z2 G4 Tower Workstations in my firm's AD environment, we are replacing all the existing Z210 workstations because of the looming windows 7 EOS on January 14th and the fact that the new machines are speed demons compared to the old ones 🙂

 

They have been sitting in their factory boxes for most of the year, we bought them in January of 2019 to avoid the price increase due to the trade tariffs that went into effect in Q1. But the schedule to deploy them was not to happen until Q3 or Q4 of 2019 due to scheduling conflicts

 

The machines have a factory build of 1809, and regardless of whether you tell the OOBE setup on first boot that you want to skip the new feature release for now or not, once you hit the desktop, and look at windows update settings (NOT check for updates) you will see that 1903 at the very least is already being downloaded. 

 

The first two machines I deployed were in early Q3 2019, so no problems there, 1909 was not available in windows update at that time for the Z2 G4

 

On the third machine I deployed in Q4 2019, the Z2 G4 apparently was okayed for 1909 by that time. I was doing my usual thing of downloading and installing all Windows updates and then subsequently HP Image Assistant driver and firmware updates when I hit the wall: 1909 went in on the next check for updates after 1903 completed installation, because I did not have "defer feature updates" set  yet (it was still at 0), but I didn't mind having the latest update in there (what could go wrong??), so I went forward.

 

I was surprised to find that I got the same error  "HP Image Assistant does not support Windows 10 version 1909 for this platform" 

 

First thing I tried to do was roll back the feature update. 

 

That turned out to do something un-intuitive, and it rolled all the way back to 1809.

I think this has something to do with the fact that 1909 is just an enablement package; all the code for 1909 was pre-installed with the 1903 feature update, Microsoft just decided when they wanted to flip the switch and called it a feature update. Rolling it back as far as windows installer was concerned rolled the whole 1903 / 1909 package back 

 

This left the formerly pristinely set up windows 10 installation in a state I don't like to build a long term user platform on top of.

 

I am pretty methodical when I deploy PCs, and , as such, always take a Clonezilla image of the hard drive in it's factory pre-boot state before I begin setup. This has saved my bacon in the past and helped in this case.

 

I restored the factory image, re-did the setup, and immediately changed the Advanced windows update settings to defer feature updates for up to 365 days. I discovered later on that this is worded misleadingly. It does not "allow you to defer" feature updates, it just plain DOES defer them for that many days as far as I have been able to determine from my research and first hand observation. I am not sure that the Quality updates setting does the same thing, I believe that one actually determines how many times you can hit "defer updates for 7 days" "Defer updates for 7 more days" 

 

Anyway, I now have a reliable way to make sure that 1903 gets in and 1909 does not, but I would much rather deploy the PCs with the latest feature update installed and HPIA run afterward to make sure all the vendor specific drivers are put in place of any generic ones (if that is even how things are done anymore with windows 10 in the mix) 

 

Has anyone here successfully run HPIA against a 1909  build Z2 G4? If so, what was the approximate date you did it?

 

TL;DR ahead, but in case anyone is interested 

 

Note to any who have not used Clonezilla live, it is superior to any hard drive imaging product I have used in the last 25 years in terms of performance in the way I use it. Not only that, it is free: it is open source and maintained constantly. It runs on a linux distro, and you can easily download the .iso file and use tuxboot to write it to a USB thumbdrive to make a bootable imaging tool.

 

I like to be able to turn a PC around quickly without having to do a wipe and reinstall and endless updates all over again, and I like to have images to cover the following scenarios:

 

  • an end user who nerfs their own PC somehow to the point that I don't trust the state of the registry or can't repair system files in a way that makes me warm and fuzzy,
  • an employee leaves the company and the PC is turned around for another user with the same workflow requirements
  • a PC needs to be turned around for a completely different workflow user

I tend to take images at these stages so I can start only as far back as I need to given the scenario.

 

  1. Factory Pre-Boot
  2. All Microsoft and PC vendor driver / firmware updates installed, windows hostname changed to HP-2UAxxxxxxx (xxxxxxx being the PC's serial number),  itsupport as the windows username, non microsoft account user profile
  3. All bloatware removed, a full set of utilities installed using ninite and or manual installation, (sysinternals suite, pdf creator, putty, SCP, filezilla, beyond compare, treesize, and any office software that we have volume licenses for, etc etc. Still in WORKGROUP with itsupport as the only user
  4. Joined to the AD domain, perfectly set up for the workflow of the end user it is slated for, including all the basic software everyone in the office uses, and any additional software that is particular to them (lacerte and turbotax for CPA dept, Factset for financial analysts, etc) their bookmarks, Outlook profile set up with cached exchange mode turned off (smaller clonezilla image) signatures, Office pinned file lists, etc etc all copied over, NO DATA moved over from their old PC, no aftermarket endpoint protection

I don't have to go back to those images often, but when someone's machine is hosed, or a new hire comes on with ZERO lead time and we have a PC in inventory that is not being used, I can pull things off in a few hours or within a day depending on how far I need to go back in the image chain given the requirements. 

 

I am the only IT pro at my firm, and having stuff like this to fall back on really reduces the pucker factor when my plate is already full and a PC turnaround is dropped in my lap 🙂

 

 

 

HP Recommended

81c5.JPG

I am an HP Employee.

If you like my post, click the thumbs up.
HP Recommended

Once i got the machine fully updated with HPIA at the 1903 level a couple of hours ago, I took a clonezilla image of it, and allowed windows to update to 1909. And I tested running HPIA and yes sir, it does work, thank you for the reply.

 

I was going to post my own update here once I was done with the workstations completely, But you beat me to it 🙂

 

Thanks.

 

However, I noticed another problem that I will address perhaps in another thread.

 

Namely, somehow during the updating procedure I noted above (MS first and then HPIA) I find myself with Intel Graphics Command center AND Intel Graphics Control panel apps installed.

 

I get a notification on the last boot after all the updates are done (including the update to 1909) telling me that I should uninstall the Intel Graphics Control Panel application, with a button marked uninstall.

 

It takes me to apps and features, but there is no uninstaller there for Intel Graphics Control panel.

 

Right clicking on the desktop and selecting "Intel Graphics Settings' brings up the Intel Graphics Control Panel (legacy?) app, but searching on the start menu does not find anything but the Intel Graphics Command Center. Both will launch without incident...

 

The only place I seem to see a possibility of uninstalling  IGCP would be in device manager | software components

 

Any advice on this would be great, I am going to leave them both in place for the time being because I really have to keep the deployment moving along.

 

 

HP Recommended

I will pass this information along to the Workstations graphics team to make them aware if they are not already aware.  This could be an issue of a legacy and DCHU driver both competing for installation.

 

Joel

I am an HP Employee.

If you like my post, click the thumbs up.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.