-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Archived Topics
- Notebooks Archive
- Re: HP AMD Carrizo A10-8700P

Create an account on the HP Community to personalize your profile and ask a question

05-10-2017
11:33 AM
- last edited on
05-10-2017
11:41 AM
by
danny-r
am unable to find hp software aggrement wher it mention about software fault so tody technican also visite my house and he submit his report that that problem unable to fixed. i need all those document please help me out
05-10-2017 12:05 PM
@RAJAT6 and @Schrammbo - counsumer courts and all will not be able to solve the problem at hand - and I am keeping the discussion fully technical here. As I have told earlier, the problem could have happened with any processor on any laptop. I faced mulitple issues with Dell laptops with Intel processors while upgrading to Windows 10, also with Lenovo laptops with older AMD processors. The issues, however, were less distrupting than this one. I'm not supporting HP with how they are working on this, but I am pretty sure that there is no gurantee that other laptops will not face the same issue too.
You need to understand that Windows 10 IS NOT A PRODUCT ANYMORE. IT IS A SERVICE. Microsoft performs some internal testing and makes the service available to the insiders. There are different levels of insiders, you must be aware of that. Usually most (but not all) bugs are fixed in the insider rings before general public gets their WIndows updated. Some bugs leaks out to general public too. Microsoft was aware of the AMD A10 issue, but released it, because they have a plan to stick to and compatibility with just one processor is something that should not hold them back.
Previously, there has been issues with Windows Updates, with Microsoft Edge, and also with drviers. Even Microsoft's own Surface devices experienced device specific issues, just like we did. However, Microsoft was quick in fixing that because the hardware and the software is from the same company. We are experiencing a delay because it is two different companies.
However, the scenario is entirely different for Enterprise users and those on LTSB. LTSB stands for Long Term Servicing Branch. If you have ever used Enterprise editions, or even LTSB editions, you will understand how much buggy final release of consumer versions of WIndows is. LTSB gets feature updates very rarely, like once a year or so and it stays bug free.
So, it takes a complete year for Microsoft to come up with Windows that is completely bug free. Microsoft releases Pro and Home versions twice a year. These are incomplete and have bugs. The bugs can crop up on any device, on any version. Even final public releases have bugs that re patched later.
You need to understand that no system is entirely bug free, especially when we are talking about complicated software, such as Operating Systems that have too many moving parts. But this is certain, that the problem can be addressed using software only. The hardware does not require any modifications. So, I'll ask you guys to hold on a little longer. A lot of us are talking about it in the Windows Insider forums. Both Microsoft and HP are working on it. But the pace is not as fast as you and I thought of.
So, right now, the best you can do is wait. No HP tech support or Microsoft tech support will be able to solve it right now. If you take it to the court, HP will roll back your device to the version of Windows 10 it came with. That's the device you bought - that's what you paid for, and it's completely working. None of HP's agreements mention anything about the device life cycle and Windows 10 support in future. Not just HP, no other OEMs have these either. I hope you understand the matter.
05-11-2017 11:45 PM - edited 05-12-2017 03:22 AM
I see this post (above) and in a try to find a solution I thought maybe...maybe it is someone to try upgrade the windows to Creator update using an older BIOS version (F.13 Rev.A or F.17 Rev.A). I don't know, maybe it is combatible...???
There is this possibility?
edit
I can't downgrade the BIOS version, must have BIOS administrator rights (?)...Needs a specialized process
[maybe must delete this duble (in other thread) post but i can't]
05-18-2017 11:43 AM - edited 05-18-2017 11:45 AM
Please you can see this post (new BIOS update from HP)
05-18-2017 01:27 PM - edited 05-18-2017 01:42 PM
The same here, after new BIOS update (F.45 Rev.A, 17 May 2017) from HP, SUCCESSFUL update (not clean install) to Microsoft windows Creators Update (without any change to BIOS settings) !!!
Thanks to all of you and
THANKS to HP !
05-18-2017 03:16 PM
I just updated my bios to f45 rev A. First thing that i noticed without changing anything (not to bios not to windows) is that the hardware reserved memory decreased from 1.1Gb to 564Mb. As it was before updating my computer to f43 rev A.
Still windows update thinks that my computer is updated fully (even if i am running 14393.1198). I will wait to update to CU normally via windows update. If not i will use the assistant file. But i am glad that we dont have to disable the tpm or do something tricky in order to have the CU update 🙂
Thank you guys 🙂 At last our computers are back to normal again 😄
