quemar deronn rafaelo
Ling Kliment
I just bought an HP Compaq pro 6300 (SFF 8 Gb ram, 120 SSD primary drive) and everything is working great except the usb blue 3.0 ports are only working at 2.0 speed - 24Mbs, the same as the 2.0 ports. Installed drivers are intel 3.0 extensible host controller and intel 3.0 root hub. I have uninstalled and reinstalled these drivers. OS is Windows 7 (64) up to date. Your site says the TI driver is the correct 3.0 driver but windows disagrees and won't use it. I have a TI 3.0 express board which works , 54Mps but I would like to use the ports supplied on this machine. I am using a 2TB WD My Book as a backup and it has always worked at 3.0 speeds on my previous computer and on the TI card.
Wong driver. When I set this computer up I installed an update from "Snappy driver tool" . It was a newer extensible host controller driver. I found one here, older, and rolled it back and now the 3.0 port is working just fine.
this pack contains all drivers of your hp computer with the right versions in info files that means you must install them manually . before installing the drivers , uninstall current version and restart your computer. then install usb3 controller with the version 214 (you must just select the folder of the drivers, windows will find the right one) and resrat again . it will work OK
e.g. I have already installed a licensed copy of MS WORD and it would be ideal if 21H2 preserved all existing programs and files. I would rather avoid needing to re-install all third-party software again.
Has Microsoft perhaps offered a single-purpose utility to verify whether or not all installed drivers are compatible with pending Windows Updates and/or upgrading to newer versions of Windows 10?
Device Manager continues to list an IDE device, even though there is no PATA socket anywhere on the motherboard; and, the .pdf User Manual also confirms that this PC does not support any IDE / PATA storage devices e.g. old PATA HDD or ODD.
For example, one ASUS motherboard has 2 x integrated Gigabit LAN controllers: one PCIe and one PCI. I ENABLE the PCIe one, and DISABLE the PCI one. These settings have always worked smoothly with all of our ASUS motherboards.
My BEST GUESS, as of today, is a very subtle bug in the latest motherboard BIOS: for example, I have also DISABLED the 1 x PCI slot in that BIOS. Such a bug may be associated somehow with that change e.g. I can try ENABLING it to see if that makes any difference.
I enabled WinUpdateStop, because of all the published complaints about Windows Update. That was a wise decision, in retrospect, because it rendered this HP workstation VERY stable over the course of many years.
A search of the Internet for that error code finds results that suspect a device driver as the reason for the ROLL-BACK and fatal error code. But, our efforts to locate such a driver in the update logs turned up empty.
software related issues can be hard to pin down and since you are using a old release of win 10 currently and having problems with a in place update, consider doing a clean install, this method can save you much time and frustration I personally have a 6300 pro (SFF model) which uses the exact same motherboard,.. and windows 10 22H2 64bit installs without any issues and includes all necessary drivers for this models hardware short of some add in discrete video cards and printer drivers i would simply backup your existing data, download the win 10 installer of your choice (usb key or Iso) install the OS and be done with it
I agree with HP about wiping the hard drive and installing a fresh copy of Windows as something is clearly amiss with the existing Windows installation with no end in site of possibly getting it fixed after six days of troubleshooting.
I fully appreciate why you are advising that probable solution, and I am sincerely grateful and understanding why it may have potential, and could succeed assuming I am willing to re-install ALL third-party software and similar system management utilities.
(2) the majority of professional opinions point to some device driver that is not identified any further in any of those opinions, however; at best those opinions recommend disconnecting ALL peripherals and resorting to more trials-and-errors
(10) it is very UNLIKELY that the driver for the Highpoint RocketRAID 2720SGL RAID controller is the culprit, because both PCs host the C: system partition on that same add-in card, and the long Windows Update process must perform HEAVY I/O with that add-in controller
(11) further research of relevant documentation on the Internet confirms that the error code in question has been occurring on many PCs worldwide: reportedly it is the single most frequent error code being reported to Microsoft during the past 2 years
(12) if verifiable, the reports summarized at (11) above would strongly suggest that Microsoft escalate that error code by dedicating capable in-house engineering expertise to identify the source(s) of that error and to publish one or more effective solutions
(13) specifically, any Microsoft software that issues that same error code can and should be modified to add more executing code that attempts to identify any suspicious device driver(s) and/or to report any other diagnostic information that can help Windows Update to complete successfully withOUT a total ROLL-BACK
(15) I am going to the trouble of documenting all of the above, because the level of details above may come to the attention of experts at Microsoft who are capable and in a position to escalate this frequently occurring error code, given the large number of Microsoft customers who are experiencing the same or similar faults.
Another option arose last evening: used versions of this PC are very cheap at eBay now, and a few of them might still have older BIOS versions. I should be able to transfer all peripherals and add-in cards to the same motherboard but with an older BIOS version.
Because this PC continues to operate smoothly and reliably with Windows 10 version 1909, I am very reluctant to tear it down merely to get Windows Update working without that fatal error code and a total ROLL-BACK.
BAD: VIA USB 3 Root Hub driver is currently version 6.1.7600.4903; the newest version according to AVG Driver Updater is version 6.1.7600.5601, but Device Manager did NOT succeed in updating that driver to that newest version.
On the contrary, WinUpdateStop has allowed this PC to work reliably and productively for many years. It has helped me AVOID ENTIRELY all of the messy and unending problems that Susan has documented in such enormous details over a period spanning YEARS.
If I do decide to continue trouble-shooting, my curiosity alone recommends purchasing a very cheap, used, version of this same motherboard, as a means to confirm whether or not a prior motherboard BIOS version cures the problem that keeps repeating with the ROLL-BACK etc.
The Windows Plug-and-Play subsystem should NOT be loading a device driver for a device that is DISABLED in the motherboard BIOS. This is how ALL of our ASUS motherboard BIOS subsystems function properly.
So, this morning I removed that add-in card and replaced it with a new Vantec UGT-PC345 USB 3.0 adapter; Windows 10 configured it automatically and installed the correct device driver without requiring user intervention.
That may be an important clue, because the C: system partition on this PC is hosted on a fast RAID-0 array, and the integrated SATA ports host 2 x JBOD SSDs, 1 x JBOD HDD and 1 x ODD (4 x SATA ports total, designated SATA0, SATA1, SATA2, SATA3).
We have not suggested you buy a new SSD.
We have suggested you make an image backup, preferable to an external USB HDD (cheap). You should be doing this anyway.
Install over the top on the existing internal disk, then try the 22H2 update.
Windows 10 22H2 is the last version of Windows 10, so if they are not Windows 11 compatible and Microsoft does not change Windows 11 requirements they will not get more feature updates although monthly patches will continue.
And, documenting my experience, while trying to do so voluntarily, may be useful to others who are similarly situated, and/or to MS software engineers who are more than capable to appreciate what is written in this long and involved Topic here.
Restoring a working drive image of C: merely requires that one BIOS change to a backup boot drive. Then, restore tasks using Acronis True Image WD Edition can run at full speed, because all device drivers are available in the migrated copy of the OS system files.
If I were an MS software engineer, I would suspect the scrambled network drive letters are connected somehow to backup copies of the OS that are stored on our secondary SSD(s) and/or secondary HDD(s).
As I believe I already mentioned, my BEST GUESS is that the original owner may have installed a PCI add-in card to add a 40-pin PATA socket. Someone probably removed that add-in card withOUT using Device Manager to remove the driver too.
Also, the tests I have already run to date appear to prove that assigning drive letters to System Reserved and cloned OS partitions made no difference whatsoever: the SFF PC wth the exact same motherboard updated AOK to 22H2 the first time.
(7) MAR staff physically removed that PCI add-in card, but without using Device Manager to remove the related device driver files: this would happen if MAR purchased a bulk of many PCs, and to save time MAR staff did not STARTUP each PC to access Device Manager
(10) for some strange reason, Windows 10 Plug-and-Play continues to detect a hardware controller that requires those driver files, EVEN THOUGH that add-in card is no longer installed in the one legacy PCI expansion slot
(14) the test at (13) is relatively easy to perform, because there is nothing installed in that one legacy PCI expansion slot; that chassis slot is currently populated with a small exhaust fan to help cool the Highpoint RAID controller installed in the x16 expansion slot that is right next to that PCI expansion slot.
c01484d022