chrqyn fayinah gaspar
Jenelle Centeno
Thank you for responding to my query. It seemed hopeful when I downloaded the suggested link unfortunately - when i installed it it said the version i had was newer and the installation would now close. Back to square one - where my HP assistant isn't working
Greetings, I'm having issues with getting the correct and most up to date HP support assistant. I've tried the Generic 9 Version and Legacy version and they don't work correctly.When I run the auto update on the HP site it doesn't specify any Support Assistant.
In this article you'll learn how to install and run the old version of the .NET Upgrade Assistant command-line interface (CLI) tool. Starting with version 0.5.2, the code base for the .NET Upgrade Assistant CLI tool was rebased on the Visual Studio extension. This means that there are effectively two different CLI tools, the version prior to 0.5.2 which is referred to as the legacy version, and the 0.5.2+ version which is the current version.
The legacy version has some functionality that is not yet available in the new version such as analyze command or solution-level upgrades, but also lacks new improvements available in the new (0.5.2+) version. Therefore, you may want to use it until the current version increases in capability and scope.
The legacy version of the tool includes an analyze mode that performs a simplified dry run of upgrading your app. It may provide insights as to what changes may be required before the upgrade is started. Open a terminal and navigate to the folder where the target project or solution is located. Run the upgrade-assistant analyze command, passing in the name of the project or solution you're upgrading.
There's quite a bit of internal diagnostic information in the output, but some information is helpful. Notice that the analyze mode indicates that during an upgrade the project's target framework moniker (TFM) is going to be set to net7.0-windows instead of net7.0. This recommendation is made because the projects referenced by the solution are WPF projects, a Windows-only technology. A console application would probably be upgraded directly to TFM net7.0, unless it used some Windows-specific library or code.
When the tool runs, it displays a list of steps it performs to upgrade the project. As each step is completed, the tool provides a set of numbered commands allowing the user to apply or skip the next step. It may provide other options such as:
When you upgrade a solution that contains multiple projects, you must select which project in the solution is the entrypoint. Based on the entrypoint project, a dependency graph is created to determine which projects to upgrade and in what order. If the solution contains projects that aren't a part of the dependency graph, they're ignored and you must upgrade these projects separately. Dependencies are upgraded first, then the entrypoint project.
Pay attention to the output of each step, as it may contain information about something the tool can't upgrade. Depending on the complexity of your app, you may have more upgrade work to do after the tool is finished.
Each step first details what it's going to do, then prompts you to do it. Any step that doesn't apply, is skipped when the tool arrives to the step. For example, if the tool processes 7. Update WCF service to CoreWCF (Preview), but your app doesn't define a WCF service, it's skipped and step 8 is processed. In turn, if step 8 doesn't apply, it's skipped too. You may see many steps skipped as the tool tries to find the next step that applies.
After you upgrade your projects, you'll need to compile and test them. Most likely there's more work to do to finish the upgrade. It's possible that the .NET Framework version of your app contained library references that your project isn't actually using, and they were carried over. Analyze each reference and determine whether or not it's required. The tool may have also added or upgraded a NuGet package reference to wrong version.
I spent last few days on Internet Searches trying to resolve driver issues related to my legacy laptop/notebook from HP.
The problem results because of the Intel Driver Support Assistant recommends and uses latest driver which conflict with OEM design and drivers HP uses; as well as new Microsoft Operating system "automated features" that are not friendly for legacy issues (default to always prioritize latest drivers). You also have to find from 3rd party sites the old legacy drivers that will still work based on "automated security features" and the automated tool preferences for "Latest drivers" (which ultimately creates the conflicts leading to failures and crashes - to include Windows no longer recognizing the adapters and various codes from 10 to 37). Brute force techniques.
I want to thank the Intel poster who experienced the problem and similar to what I am doing just posted their solution for going to a prior driver for the Intel Wireless AC 9461 from a year ago that resolved the conflict. This is a problem of the automated update tools and an OEM design that conflict and its the second time I faced this with HP product....Intel community was more helpful than HP.
Updates using the Intel tool are not always compatible with legacy software driver systems; as they (HP) no longer support updating their own drivers as Microsoft Windows goes to its newer generation versions of Windows 10/11; while automated and security features do introduce compatibility conflicts needing manual interventions. Thanks to this community for posts that help! The fine print of tools do warn of OEM conflicts - but then have to research solutions on own and a post by users with Older driver versions they found that actual worked help!
I could not find an "Official" Intel site for older drivers and for security reasons was looking for recommendation on best sources for obtaining the legacy driver for Intel chipsets as didn't find on Intels webpages.....
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
The new version of HP Assistant does not work properly or have any tools or tune ups like the old version I had. I tried to find it on my computer but only the new version is there because I deleted the old windows system files. The new version does not ask for which country I am in or anything that the website says it should ask for and what it is supposed to have included. Please help me find a link to the old version of the HP Assistant that I had with Windows 7 Home Premium addition. Its the Pavillion g7-1178ca notebook that i purchased in 2011, therefore there are no updates or drivers available for it from HP. I can't find any way to do the "tune up" which i did on a regular basis, it is no where on the new version with windows 10. Thank you for your help and time. I live in Canada.
When you look at the list of supported PC's that version is supposed to work with, I figured it would work for your model too. While it does not list the g6 or g7 series as supported, it shows much older models supported by this software.
Just so you know, we're getting a LOT of posts from folks who have upgraded their HP machines to Win10 and find out that the HP Support Assistant app no longer works for them. So, we have been posting links to the Win10 version for them.
Dear WAWood, Thank you so much for your Reply ! Could you please send me in the direction of where you have been posting links for the updated version for Windows 10. Again, thank you very much for your help, much appreciated, sincerely Niki
Dear Paul, thank you very much for the link for the new windows 10 HP Ass. I installed it, restarted my laptop then went to open it and all that happened was the logo blinked on my screen for 2 seconds and disappeared. I went too my control panel, Programs and features and it was listed there with 2.66 MB but no version. I have searched my computer everywhere and can not find it. While I was in the Programs list, I refreshed it, then restarted but that did not help.
So I downloaded the link again, said "replace All", a pop up menu came up that said "The process can not access the file because it is being used by another process", I hit ok and then it continued to install again as it did the first time. When it was finished i restarted my computer, then tried to open it and got the same result, the logo just blinked on the screen for a second and disappeared. When I right click on the blue question mark icon and hit "open" I get the same result.
Ok Paul, thank you so very much for all your help. I truly appreciate all the time you spent trying to help me with this issue. It really is too bad, I used HPSA a lot, especially the "Tune Up" on a regular basis. I am not happy with HP that they do not have any updated drivers or software for products sold before 2013, this makes our lives much more time consuming and difficult. Do they think that our computers are not worth their time? Might have to rethink about what product to buy next time i purchase a laptop. You have been great, thank you again, take care,
I have an old iMac that is running on OS X 10.6.8 and all of the new Xcodes aren't available on a Mac like mine. Could someone please tell me how to download an older version of Xcode that is available for my Mac. Also, if I download this older version, will people that are on iOS 8/9 be able to go on them? I'm guessing that in the app description it will say availble for iOS 5 and so on? Thanks for all your help!
Submitting to the store currently requires Xcode 5.1.1 or later (and I am fully expecting them to start requiring Xcode 6 with the iOS 8 SDK pretty soon). Yes apps that you build using old Xcode versions should run OK on newer OS versions but they can only be distributed ad hoc.
c01484d022