Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: sptilton on November 17, 2014, 07:51:55 pm
-
KB2884256 update fails.
SYSTEM INFO
OS Version: Microsoft® Windows Vista™ Ultimate, Service Pack 2, 32 bit
Processor: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz, x64 Family 6 Model 23 Stepping 7 Processor Count: 4
RAM: 3067 Mb
Graphics Card: NVIDIA GeForce 8600 GT, 512 Mb
Hard Drives: C: Total - 476937 MB, Free - 310685 MB; K: Total - 476936 MB, Free - 330533 MB;
Motherboard: Intel Corporation, DG31PR
Antivirus: McAfee Anti-Virus and Anti-Spyware, Updated and Enabled
PROBLEM
WINDOWS UPDATE FAILURE
The following update has failed to install since it came out last year.
All other updates properly install.
KB2884256(security update for USB drivers: October 8, 2013 )
Error code 80070002
The update appears to download OK, but I get the following message when the
computer is rebooted: "Failure configuring Windows updates. Reverting changes".
FIXIT ATTEMPS
ERROR CHECKING (SCANDISC)
Ran Error Checking (Scandisc) to fix KB2884256 update failure problem,
X Automatically fix file system errors
X Scan for and attempt recovery of bad sectors
No bad sectors found. Logical problems fixed.
This did not help.
Update still fails,
.
MicrosoftFixit.wuFISC.1933248052692592.1.1.Run.exe
MicrosoftFixit.wu.LB.9328810687104191.3.1.Run.exe
MicrosoftFixit.wu.RNP.148323629132156062.4.3.Run.exe
MicrosoftFixit50202.msi
MicrosoftFixit50624.msi
System Update Readiness tool. Windows6.0-KB947821-v34-x86.msu
Hotfix for Windows (KB947821)
None of these helped.
- sfc /SCANNOW – no problems
Tweaking.com Windows Repair v2.10.2
Update still fails
VIRUS, MALWARE checks etc.
McAffe Anitvirus including rootkit check
Malwarebytes
AVG Antivius from Linux Bootable CD including rootkit check
Malwarebytes Anti-Rootkit BETA 1.07.0.1008
RougeKiller
No problems found from any of these.
MANUAL FIX ATTEMPTS
Manually tried to download update. This did not help.
Manually tried to fix problem.
Stopped the Windows Update service, Deleted the temporary update files,
Restarted the Windows Update service. This did not work.
WINDOWS LOG INFO
WINDOWS UPDATE KB2884256 FAILURE
Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 10/4/2014 3:29:31 AM
Event ID: 20
Task Category: Windows Update Agent
Level: Error
Keywords: Failure,Installation
User: SYSTEM
Computer: Owner-PC
Description:
Installation Failure: Windows failed to install the following update with error 0x80070002: Security Update for Windows Vista (KB2884256).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" />
<EventID>20</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>1</Task>
<Opcode>13</Opcode>
<Keywords>0x8000000000000028</Keywords>
<TimeCreated SystemTime="2014-10-04T08:29:31.486Z" />
<EventRecordID>357568</EventRecordID>
<Correlation />
<Execution ProcessID="1324" ThreadID="3628" />
<Channel>System</Channel>
<Computer>Owner-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="errorCode">0x80070002</Data>
<Data Name="updateTitle">Security Update for Windows Vista (KB2884256)</Data>
<Data Name="updateGuid">{3CCC50A0-55A5-400B-9D88-0724EB4B6438}</Data>
<Data Name="updateRevisionNumber">201</Data>
</EventData>
</Event>
DEXCOM STUDIO CGM DRIVER INSTALLATION FAILURE
The driver from the Dexcom Studio program (http://dexcom.com/dexcom-studio)
fails to load.This program uses a "Virtual USB Com Driver".It gives the same
error code as the Windows update failure.
DEXCOM STUDIO:WINDOWS ERROR REPORTING (WER)
These are the log files generated from the failed attempt to install the
Dexcom drivers for the G4. The attempted driver installation was done from
inside the Studio program, using the tools menu. The operating system is
Windows Vista.
These files were located at:
C;\ProgramData\Microsoft\Windows\WER\ReportQueue\Report1c635820.
---------------------------------------------------------------------------------------------
The files "ProbReport.txt","LOG5785.tmp", and "Report.wer" contains the failure information.
---------------------------------------------------------------------------------------------
THE FOLLOWING PROBLEMS MAY BE SIGNIFICANT:
1, Win32 error: 80070002. Failed to copy driver package from source into
temporary client location. Error = 80070002,
SrcInf = c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf,
DestPath = C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d- 64f29680fdd9}
2.FriendlyEventName=Could not install driver software
ConsentKey=PnPDriverImportError
3,The driver package has a reference to a missing file. File Name = usbser.sys,
Error = 80070002 The manufacturer of the device told me where this file is
supposed to be located and the file was there.
---------------------------------------------------------------------------------------------------------------------------
DEXCOMVCPDRIVER.INF
----------------------
[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%ProviderName%
CatalogFile=DexComVCPDriver.cat
DriverVer=05/24/2010,1.0.0.2
[MANUFACTURER]
%ProviderName%=DeviceList, NTx86, NTamd64
[DeviceList.NTx86]
%AtmelEVK1105CDC%=DriverInstall,USB\VID_22a3&PID_0047
[DeviceList.NTamd64]
%AtmelEVK1105CDC%=DriverInstall,USB\VID_22a3&PID_0047
[DriverInstall]
include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=LowerFilterAddReg,SerialPropPageAddReg
[DriverInstall.Services]
include = mdmcpq.inf
AddService = usbser, 0x00000002, LowerFilter_Service_Inst
; This adds the serial port property tab to the device properties dialog
[SerialPropPageAddReg]
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
[Strings]
ProviderName = "DexCom, Inc."
AtmelEVK1105CDC = "DexCom USB/COM Port Driver"
----------------------------------------------------------------------------------------------------------------------------
PROBREPORT.TXT
--------------
Product
Driver software installation
Problem
Could not install driver software
Date
6/13/2014 9:01 PM
Status
Not Reported
Description
Windows could not copy all of the files needed to install this device driver software. This sometimes happens when the driver software was not designed for this version of Windows.
Problem signature
Problem Event Name: PnPDriverImportError
Architecture: x86
Win32 error: 80070002
Inf name: dexcomvcpdriver.inf
Driver Package hash: 34c19a05c447fc9bdd48174f6232dc357fbb62d1
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1033
Files that help describe the problem
DMI5775.tmp.log.xml
LOG5785.tmp
dexcomvcpdriver.inf
----------------------------------------------------------------------------------------------------------------------------
DMI5775.TMP.LOG.XML
-------------------
<?xml version="1.0" encoding="UTF-16" standalone="no"?>
<werData>
<driverPackageFiles><file name="DexComVCPDriver.cat" size="7519" date="05-24-2010" time="21:11"/>
<file name="DexComVCPDriver.inf" size="892" date="05-24-2010" time="20:59"/>
<file name="dpinst.exe" size="921688" date="05-25-2010" time="17:51"/>
</driverPackageFiles>
</werData>
----------------------------------------------------------------------------------------------------------------------------
LOG5785.TMP
-----------
>>> [Staging Package To Driver Store - phase 1 - dexcomvcpdriver.inf]
>>> Section start 2014/06/13 21:01:16.093
sto: Inf Path = c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf
sto: Flags = 0
sto: Processor Architecture = 0
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
sto: Copying driver package. Inf = c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf, Destination = C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d-64f29680fdd9}
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\owner\appdata\local\temp\ixp000.tmp'
flq: SourceFilename - 'dexcomvcpdriver.inf'
flq: TargetDirectory- 'C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d-64f29680fdd9}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\owner\appdata\local\temp\ixp000.tmp'
flq: SourceFilename - 'DexComVCPDriver.cat'
flq: TargetDirectory- 'C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d-64f29680fdd9}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
inf: Opened INF: 'c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf' ([strings] <src = normal>)
inf: Opened PNF: 'C:\Windows\INF\mdmcpq.inf' ([strings] <src=drvstore>)
!!! sto: The driver package has a reference to a missing file. File Name = usbser.sys, Error = 80070002
!!! sto: GetCopyFilesListFromInf() failed. Error = 80070002, Inf = c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf
!!! sto: Failed to copy the Driver Package to C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d-64f29680fdd9}. Error = 80070002
!!! sto: Failed to copy driver package from source into temporary client location. Error = 80070002, SrcInf = c:\users\owner\appdata\local\temp\ixp000.tmp\dexcomvcpdriver.inf, DestPath = C:\Users\Owner\{43b6b6e7-ba5c-42cb-b99d-64f29680fdd9}
----------------------------------------------------------------------------------------------------------------------------
REPORT,WER
Version=1
EventType=PnPDriverImportError
EventTime=130471848762790000
Consent=1
Response.type=4
Sig[0].Name=Architecture
Sig[0].Value=x86
Sig[1].Name=Win32 error
Sig[1].Value=80070002
Sig[2].Name=Inf name
Sig[2].Value=dexcomvcpdriver.inf
Sig[3].Name=Driver Package hash
Sig[3].Value=34c19a05c447fc9bdd48174f6232dc357fbb62d1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6002.2.2.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
File[0].CabName=DMI5775.tmp.log.xml
File[0].Path=DMI5775.tmp.log.xml
File[0].Flags=65536
File[0].Type=5
File[1].CabName=LOG5785.tmp
File[1].Path=LOG5785.tmp
File[1].Flags=65536
File[1].Type=5
File[2].CabName=dexcomvcpdriver.inf
File[2].Path=dexcomvcpdriver.inf
File[2].Flags=65536
File[2].Type=5
FriendlyEventName=Could not install driver software
ConsentKey=PnPDriverImportError
AppName=Driver software installation
AppPath=C:\Users\Owner\AppData\Local\Temp\IXP000.TMP\dpinst.exe
ReportDescription=Windows could not copy all of the files needed to install this device driver software. This sometimes happens when the driver software was not designed for this version of Windows.
flavallee's Avatar
flava
-
There are a number of reasons for the error, but oddly enough I did find one where McAfee was the problem
http://blog.waldrondigital.com/2009/06/30/windows-update-80070002-error-with-vista/
See if that link helps at all and let me know :wink:
Shane
-
Thanks for the reply. The file is where it belongs (see attachment). The file is not in the McAfee quarantine list.
-
It was worth a shot lol
Have you tried running the system readiness tool for vista yet?
Perhaps there is something the update needs installed first, and if that is the case the system readiness tool normally takes care of it.
http://www.microsoft.com/en-us/download/details.aspx?id=1540
Basically I want to cover all the bases first, a process of elimination :wink:
Shane
-
I have run the "System Update Readiness tool. Windows6.0-KB947821-v34-x86.msu" with no effect. I have also run the following with no effect:
Hotfix for Windows (KB947821)
MicrosoftFixit.wuFISC.1933248052692592.1.1.Run.exe
MicrosoftFixit.wu.LB.9328810687104191.3.1.Run.exe
MicrosoftFixit.wu.RNP.148323629132156062.4.3.Run.exe
MicrosoftFixit50202.msi
MicrosoftFixit50624.msi
-
Sorry for the late reply. Been slammed with work the past 2 days.
try the update again and then attach the cbs log file so I can see what errors it is giving :wink:
Shane
-
This is a test post without the CBS log text file attachment. If this posts properly it may indicate there is something in the CBS attachment that prevents posting.
-
The CBS log is huge 24.357KB with 3,768 pages. Perhaps it is too big to be attached and posted. It is attached to this post in Zip format.
-
OK I found it in the log file
2014-11-21 13:38:04, Info CBS Appl: Evaluating package applicability for package Package_for_KB2884256_server~31bf3856ad364e35~x86~~6.0.1.1, applicable state: 0
2014-11-21 13:38:04, Info CBS Plan: Skipping package since its start state and target state are both absent for package: Package_for_KB2884256_server~31bf3856ad364e35~x86~~6.0.1.1, current: 0, pending: -16, start: 0, applicable: 0, targeted: 0, limit: 7
2014-11-21 13:38:04, Info CBS Perf: Begin: nested restore point - begin
2014-11-21 13:38:13, Info CBS Doqe: Installing driver Update ID: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1~2884256-2_neutral_GDR
2014-11-21 13:38:14, Error CBS Doqe: Failed installing Update ID: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1~2884256-2_neutral_GDR: 0x80070002
2014-11-21 13:38:14, Error CBS Doqe: Failed processing queue with hr: 0x80070002
2014-11-21 13:38:14, Error CBS Shtd: Failed while processing non-critical driver operations queue. hr: 0x80070002
2014-11-21 13:38:14, Info CBS Shtd: progress thread terminating. hr: 0x0
2014-11-21 13:38:14, Info CBS Shtd: progress thread terminated normally
2014-11-21 13:38:14, Info CBS Shtd: Shutdown processing complete.
2014-11-21 13:38:14, Info CBS Restored system sleep block state: 0x80000000
2014-11-21 13:39:49, Info CBS Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\cbscore.dll
2014-11-21 13:39:49, Info CSI 00000001@2014/11/21:19:39:49.760 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73738a50 @0x7404854e @0x740263a1 @0x5a1392 @0x5a1ed4 @0x5a17cb)
2014-11-21 13:39:49, Info CSI 00000002@2014/11/21:19:39:49.900 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73738a50 @0x7407e7b6 @0x74060f93 @0x5a1392 @0x5a1ed4 @0x5a17cb)
2014-11-21 13:39:49, Info CSI 00000003@2014/11/21:19:39:49.932 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x73738a50 @0x740a1a0d @0x740a1794 @0x5a360b @0x5a2be3 @0x5a17cb)
2014-11-21 13:39:49, Info CBS Blocked system sleep; prior state: 0x80000000
2014-11-21 13:39:49, Info CBS Startup: Begin processing, registering for winlogon notification.
2014-11-21 13:39:49, Info CBS Startup: current ExecuteState is 0
2014-11-21 13:39:49, Info CBS Startup: Initializing driver operations queue.
2014-11-21 13:39:49, Info CBS Startup: Initializing advanced operation queue.
2014-11-21 13:39:50, Info CSI 00000004 CSI Store 2810344 (0x002ae1e8) initialized
2014-11-21 13:39:50, Info CBS Startup: Waiting for SC autostart event
2014-11-21 13:40:06, Info CBS Startup: SC autostart event signaled
2014-11-21 13:40:06, Info CBS Obtained poqexec from Cbs key. C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6002.18005_none_0b4ada54c46c45b0\poqexec.exe /display_progress \SystemRoot\WinSxS\pending.xml
2014-11-21 13:40:06, Info CBS Free disk space check on C:. Available: 339155MB, Required size (Lang neutral): 0MB, Required size (Per language): 0MB, Languages installed: 1, Total Required: 0MB
2014-11-21 13:40:06, Info CBS Startup: Processing non-critical driver operations queue, Count 4.
2014-11-21 13:40:06, Info CBS Doqe: Preparing install of driver Update ID: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1~2884256-2_neutral_GDR
2014-11-21 13:40:06, Info CBS Doqe: add Key: 1, Identity: mdmnis2u.inf, Culture=neutral, Type=driverUpdate, Version=6.0.6002.18927, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS, Inf: mdmnis2u.inf, Ranking: 2
2014-11-21 13:40:06, Info CBS Doqe: Lock deployment Identity: mdmnis2u.inf, Culture=neutral, Type=driverUpdate, Version=6.0.6002.18927, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS, Inf: mdmnis2u.inf
2014-11-21 13:40:07, Info CSI 00000005 Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:d0251af4c205d001010000003806c406} pathid: {l:16 b:d0251af4c205d001020000003806c406} path: [l:178{89}]"\SystemRoot\WinSxS\x86_mdmnis2u.inf_31bf3856ad364e35_6.0.6002.18927_none_9329d9ddf862893d" pid: 638 starttime: 130610723893159001 (0x01d005c2e9822459)
2014-11-21 13:40:07, Info CSI 00000006 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-11-21 13:40:07, Info CSI 00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x234
2014-11-21 13:40:09, Info CSI 00000008@2014/11/21:19:40:09.054 CSI perf trace:
CSIPERF:TXCOMMIT;1575300
2014-11-21 13:40:09, Info CBS Doqe: Installing driver Update ID: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1~2884256-2_neutral_GDR
2014-11-21 13:40:10, Error CBS Doqe: Failed installing Update ID: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1~2884256-2_neutral_GDR: 0x80070002
2014-11-21 13:40:10, Error CBS Doqe: Marked package Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1 as failed
2014-11-21 13:40:10, Error CBS Doqe: Failed processing queue with hr: 0x80070002
2014-11-21 13:40:10, Error CBS Startup: Failed while processing non-critical driver operations queue. hr: 0x80070002
2014-11-21 13:40:10, Info CBS Removed poqexec from Cbs key.
2014-11-21 13:40:10, Info CBS Removed CCP impactful-commit disabling value
2014-11-21 13:40:10, Info CBS Setting ExecuteState key to 2
2014-11-21 13:40:10, Info CBS Setting ExecuteState key to 20
2014-11-21 13:40:10, Info CSI 00000009 Creating NT transaction (seq 2), objectname [6]"(null)"
2014-11-21 13:40:10, Info CSI 0000000a Created NT transaction (seq 2) result 0x00000000, handle @0x1e0
2014-11-21 13:40:11, Info CSI 0000000b@2014/11/21:19:40:11.660 CSI perf trace:
CSIPERF:TXCOMMIT;631751
2014-11-21 13:40:11, Info CBS Failed removing impactful-commit disabling value from CCP. hr: 0x80070002
2014-11-21 13:40:11, Info CBS WER: Generating failure report for package: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1, status: 0x80070002, failure source: DOQ, start state: 4, target state: 8
2014-11-21 13:40:34, Info CBS Startup: Package: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1 completed startup processing, new state: Staged, original: Staged, targeted: Permanent. hr = 0x80070002
2014-11-21 13:40:34, Info CBS WER: Generating failure report for package: Package_for_KB2884256_client_2~31bf3856ad364e35~x86~~6.0.1.1, status: 0x80070002, failure source: DOQ, start state: 4, target state: 8
2014-11-21 13:40:34, Info CBS Startup: Package: Package_for_KB2884256_client_2~31bf3856ad364e35~x86~~6.0.1.1 completed startup processing, new state: Staged, original: Staged, targeted: Permanent. hr = 0x80070002
2014-11-21 13:40:34, Info CBS WER: Generating failure report for package: Package_for_KB2884256_client~31bf3856ad364e35~x86~~6.0.1.1, status: 0x80070002, failure source: DOQ, start state: 4, target state: 8
2014-11-21 13:40:35, Info CBS Startup: Package: Package_for_KB2884256_client~31bf3856ad364e35~x86~~6.0.1.1 completed startup processing, new state: Staged, original: Staged, targeted: Permanent. hr = 0x80070002
2014-11-21 13:40:35, Info CBS WER: Generating failure report for package: Package_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1, status: 0x80070002, failure source: DOQ, start state: 4, target state: 8
2014-11-21 13:40:35, Info CBS Startup: Package: Package_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1 completed startup processing, new state: Staged, original: Staged, targeted: Permanent. hr = 0x80070002
2014-11-21 13:40:35, Info CBS Startup: Package: Package_2_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1 completed startup processing, new state: Staged, original: Staged, targeted: Permanent. hr = 0x800f0826
2014-11-21 13:40:35, Info CBS Setting ExecuteState key to -1
2014-11-21 13:40:35, Info CBS Setting RollbackFailed flag to 0
2014-11-21 13:40:35, Info CBS Startup: Signaling caller to retry failed packages.
2014-11-21 13:40:35, Info CBS Startup: Processing complete. hr: 0x80070002
2014-11-21 13:40:35, Info CBS Restored system sleep block state: 0x80000000
2014-11-21 13:40:38, Info CBS PA-RA: Querying for PAC queue values...
2014-11-21 13:40:38, Info CBS PA-RA: No pending packages found.
2014-11-21 13:40:38, Info CBS Session: 30410179:111295024 initialized.
2014-11-21 13:40:38, Info CBS RA: Searching for packages to retry...
2014-11-21 13:40:38, Info CBS RA: Skipping package: Package_1_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1, target state not installed or absent: 8
2014-11-21 13:40:38, Info CBS RA: Skipping package: Package_2_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1, target state not installed or absent: 8
2014-11-21 13:40:38, Info CBS RA: Skipping package: Package_for_KB2884256_client_2~31bf3856ad364e35~x86~~6.0.1.1, target state not installed or absent: 8
2014-11-21 13:40:38, Info CBS RA: Skipping package: Package_for_KB2884256_client~31bf3856ad364e35~x86~~6.0.1.1, target state not installed or absent: 8
2014-11-21 13:40:38, Info CBS RA: Skipping package: Package_for_KB2884256~31bf3856ad364e35~x86~~6.0.1.1, target state not installed or absent: 8
From what I can find on these error codes, looks like there is a service it needs to be running in order to install.
Some users reported that these services need to be running
Windows Modules Installer
Windows Update
Task Scheduler
Group Policy Client
Plug and Play
In fact the dexcon error you got shows the PnP error (Plug and Play)
2.FriendlyEventName=Could not install driver software
ConsentKey=PnPDriverImportError
So double check that those services are running.
Shane
-
I checked the Services with the following results:
Windows Modules Installer Manual
Windows Update Started Automatic
Task Scheduler Started Automatic
Group Policy Client Started Automatic
Plug and Play Started Automatic
PnP-X IP Bus Emulator Manual
I changed the Windows Module Installer and the PNP-X IP Bus Emulator to Automatic, then rebooted the computer. Both services now said they were "Started" but were listed as "Manual". Both the Security Update and the Dexcom driver installation failed after making the changes.
-
While Windows Update doesn't work in Safe Mode with Networking, can you try the direct download in that mode should it be McAfee that is blocking.
If that doesn't do it then open a command prompt as an admin and copy & paste these commands where they will auto run.
If any seem to hang then press enter.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
-
I have tried both techniques before without success. I also suspect that one or more of the Windows Fixit programs I used just automated your command line technique.
-
If you haven't already tried Windows Installer 4.5 give it a try. http://support.microsoft.com/kb/942288
-
It appears I am already running Windows Installer 4.5 (see attachment).
-
Have you checked Device Manager/View/Show hidden devices for any yellow alerts, possibly against Non-Plug and Play Drivers ?
Can you uninstall Dexcom, retry Windows Update or reinstall Dexcom to see if its driver update will install then and are you loading the driver for Vista ?
-
I just rechecked Device Manager. There are no yellow alerts. However, back on 11/11/14 there was a yellow alert under "Network Adapters" for the "Teredo Tunneling Pseudo-Interface". I was able to fix that, but it made no difference for the present problem.
If I plug in the Dexcom CGM device to any USB port, I do get a yellow alert because the driver is missing (see attachements). The normal Windows technique for finding the driver on line, on the computer, or on the Dexcom Studio CD fails to find it. It fails to install when the program is removed and then reinstalled. It fails to install when reinstallation of the driver is tried from within the program. It tries to install something called a " Virtual USB\COM driver" (see attachment)., but always fails.
The KB2884256 update came out and failed long before the Dexcom Studio program was installed. I thought they might be related because the error codes are the same and the update deals with USB drivers.
All other updates before and after KB2884256, which came out over a year ago, have loaded properly.
I tried the normal automatic and then the manual update technique. I even found a copy of the update online and downloaded it so I could try installing it off line. I tried doing it in Safe Mode. I tried using "Selective Startup" in "Diagnostic mode". All techniques failed in the same manner.
The only plug and play I could find in the Device Manager was under "System devices" as "Plug and play software enumerator" (see attachment). There are numerous listings under "Non plug and play drivers".
-
Hello Im on windows 7 64 bit , i changed from windows vista then suddenly i couldnt update any driver but i can still use my mouse and keyboard, I tried tweaking.com and installing from manufacturer's website but stll i always get "acess denied" repair but the problem still exist. Help will be really appreaciated. Thanks
-
Hello Im on windows 7 64 bit , i changed from windows vista then suddenly i couldnt update any driver but i can still use my mouse and keyboard, I tried tweaking.com and installing from manufacturer's website but stll i always get "acess denied" repair but the problem still exist. Help will be really appreaciated. Thanks
You will need to open a new thread of your own as two different solutions may be required.
-
@ sptilton
I'm not familiar with Virtual USBs but the South Bridge of either Chipset or the video drivers looks after the Bus Controller for USBs and downloading the Chipset and/or Nvidia drivers may help.
If neither Dexcom or Windows are able to find the Dexcom driver then perhaps the free version of Slimdrivers may have better luck ?
Look out for the box to uncheck for MyPCBackup during the installation prompts. http://www.driverupdate.net/
-
I updated the Intel DG31PR chipset driver from version 8.4.0.1016 to the latest version 9.1.2.1008 on 10/12/14 to try to fix this problem. It did not help. The Device Manager says the Nvidia driver is working and up to date.
The Dexcom Studio program does seem to find the driver, but Windows will not load it, because it says it can not find a missing file that is there (see Dexcom7.jpg, and post 1 under "DEXCOM STUDIO CGM DRIVER INSTALLATION FAILURE"). I believe the Dexcom CGM uses some sort of USB to UART Bridge VCP Driver.
I did find a problem that may be significant while checking updates thru the Device Manager. It appeared under "Human Interface Devices" , "USB Human Interface Device". There were two of these. The drivers were working, but updates were available. When I tried to update either one I got the error message "This operation requires an interactive Window station"(see attachment DriverUpdateProb.jpg).
-
I never use the driver update option in Device Manager as Windows very rarely has up to date drivers so I'd try the computer support site for any Nvidia updates.
That's a new error message for me and a Google has suggested a repair install, deleting the restore points, disabling AV program/firewall, or uninstalling the devices in Device Manager and letting Windows reinstall them either through Action/Scan for hardware changes or a reboot - which is the one I would favour after first creating a restore point.
Having Googled Dexcom I appreciate the importance of this program, but if it's working okay, do you really need to update any drivers ?
It's generally advised (that I've seen), that if something is working fine then leave any driver updates until it isn't - but this doesn't resolve the failure of KB2884256 or why Windows is reporting it is unable to find that file.
-
The driver for the Dexcom Studio program fails to install. There is no driver to update. The one that fails to install is the only one. The program runs, but is useless without a working driver. The data from the measuring device can not be downloaded into the program for analysis without a working driver.
-
I see.
I don't have an answer as to why Windows cannot find that file but hopefully Shane will be able to sort when he returns, either later today or Monday.
Did you try creating a restore point and then uninstalling those USB Human Interface Devices to allow Windows to reinstall them ?
-
I have a feeling the problem may not be the driver or the windows update but instead the current drivers loaded for the normal USB.
Try this, might be hard if you have a usb mouse. But in the device manager have it set to show hidden devices, then go and uninstall every usb device there is that you can. So in the device manager go to the universal serial bus controllers and remove them all and then reboot, letting windows reinstall them.
When windows reinstalls them it should update the drivers and registry locations for them. I had this problem on a customers machine a while back and this was the trick that I got to fix it. It was one of the usb controllers that was causing the problem.
Shane
-
In "device manager" I have four areas that mention USB. One area is under "universal serial bus controllers". The mouse and keyboard have their own sections. I am not sure which ones I should try removing. Just the ones under "universal serial bus controllers" or some or all of the others (see attachment). Both my mouse and keyboard are USB. So what, if any, is the process for removing the mouse and keyboard and still controlling the computer?
-
I found my computer has unused keyboard and mouse PS2 ports on back. I do not see these listed in the device manager, but would guess they are the "HID-compliant consumer control device" and "HID-compliant device" under "Human Interface Devices" (see attachment). I will test to see if I can use a PS2 keyboard and mouse on these ports. Let me know which devices in the previous post I should remove.
Thanks
-
If you can use a ps2 mouse then remove them all, do all the usb ones first.
Shane
-
I tried your suggestion of uninstalling all the USB devices in the "Universal serial bus controllers". This did not work. All failures still occur.
I am not sure I got all USB's, but those were the only ones listed after changing mouse and keyboard to PS2.
I had shut down the computer and replaced the USB keyboard and mouse with PS2 types. When I turned it back on and locked in the Device Manager the only USB devices listed were under "Universal serial bus controllers". The one labeled "USB composite device" under this heading had disappeared. I think that might have something to do with the keyboard. Now there were eleven instead of twelve under this heading.
The "Human interface devices" and all devices under that headings disappeared.
The mouse and keyboard were now listed as PS2 and worked properly.
-
RE: USB keyboard and mouse drivers fail.
I shut down the computer to remove the PS2 devices and put back the USB keyboard and mouse. When I restarted, the drivers started to install, but the USB keyboard and mouse drivers failed. The keyboard and mouse did not function. I rebooted and did a "restore point" using the Windows installation disc . This made the USB keyboard and mouse functional again.
Attached are some "Event Viewer" and "Problem Reports and Solution" logs that may be relevant.
-
When I restarted, the drivers started to install, but the USB keyboard and mouse drivers failed.
Then that confirms it, the program is the USB and possibly its drivers. The USB itself is fine, it is the registry settings, keys and such in Windows that is messed up for it, and pretty much anything you try to have install over the usb simply fails.
So it is dexcon or Windows updates, but instead Windows itself. Problem is I dont have a clue what registry keys to look for because I dont know what Windows is looking at when it is installing drivers for a USB device.
So the fastest way is to do a repair install, not a fresh install. With a repair install you keep all your programs and settings. It does carry over drivers through, so curious if the problem will follow or get corrected.
But to do a repair install you need a vista cd with sp2 already on it. And then follow this :wink:
http://www.vistax64.com/tutorials/88236-repair-install-vista.html
Shane
-
I wonder if going to the computer support site if OEM build or the motherboard support site if custom build and downloading the Intel Chipset drivers before the repair install would help ?
-
Thanks for the info. I have previously tried a repair from the installation CD with no effect. But the CD is pre SP2. If I understand the info in the link it seems this will not work. The link says:
"If you have an Anytime Upgrade Vista installation DVD, then you will not be able to do this."
"IF YOU HAVE THE VISTA SP2 INSTALLED:
This will not work if you have SP1 and SP2 installed unless your
Vista installation DVD includes SP2."
Unfortunately my disc is an "Anytime Upgrade" and does not include SP2.
I tried doing repairs to SP2 but the computer can not find the files (see attachment).
I found this link on "How to Create Free Windows Vista SP2 Recovery Disk"
( http://www.ehow.com/how_8645148_create-vista-sp2-recovery-disk.html )
Does this seem feasible?
Thanks
-
I updated the Intel DG31PR chipset driver from version 8.4.0.1016 to the latest version 9.1.2.1008 on 10/12/14 to try to fix this problem. It did not help.
-
I updated the Intel DG31PR chipset driver from version 8.4.0.1016 to the latest version 9.1.2.1008 on 10/12/14 to try to fix this problem. It did not help.
It was just a thought that may have saved you from the repair install.
That link for the Recovery disk would only get you a disk that would boot you into the F8 options.
From a Google you would need to create a Vista ISO boot disk and then Slipstream SP2 into it and this is what I've found for those -
http://www.mydigitallife.info/64-bit-x64-windows-vista-official-direct-download-links/
This is one from clicking on a sub link in that article which includes how to make a bootable disk from those files. http://www.mydigitallife.info/windows-vista-free-direct-download-link/
This article may also help if you want to go for the Vista SP1 ISO http://www.heidoc.net/joomla/technology-science/microsoft/57-windows-vista-direct-download-links
http://www.ehow.com/how_6100639_slipstream-vista-sp2.html
Hope these help but if you have any problems I'm sure Shane will be able to guide you.
Don't forget that you will need your generic product key as the sticker key doesn't always work and which Belarc Advisor will display for you. http://www.belarc.com/free_download.html
-
Before trying to create the ISO boot disk, is replacing the INFCACHE.1 file as described at http://www.instant-registry-fixes.org/resolve-windows-vista-usb-detection-issues/ worth a try.
Is this fix relevant?
-
Before trying to create the ISO boot disk, is replacing the INFCACHE.1 file as described at http://www.instant-registry-fixes.org/resolve-windows-vista-usb-detection-issues/ worth a try.
Is this fix relevant?
I don't know if it's relevant to Virtual USBs but you could always give it a try - but create a restore point first before making any changes.
-
RE: Installing Windows Automated Installation Kit – WAIK?
According to Brightbulb (http://www.brighthub.com/computing/smb-security/articles/53735.aspx) I need to "start off by installing the .NET Framework and WAIK." I need to know how to install the WAIK program from the image file (http://www.microsoft.com/en-us/download/details.aspx?id=10333). Even if I extract the files and folders (see attachment), how would the program be installed and run?
-
All right, do not waste you a lot of time, download the software on dell-drivers-download.com (http://"http://www.dell-drivers-download.com"), and it can help you automatically find the drivers you need, and get them downloaded for you only with a few clicks. do not hesitate, just have a try, please!
-
If you have created the Vista SP1 ISO version boot disk then read through the following article for how to uninstall SP2 so that you will be able to use the SP1 disk to repair your system, but create an external system image first - either to DVDs or an external HDD before uninstalling SP2.
If you haven't created the disk which includes SP1 then go back to my reply #33 for that link and the relevant SP1 ISOs are lower down the page and this should avoid the problems in streaming SP2..
You can reinstall SP2 after the repair is complete.
http://support.microsoft.com/kb/948537
http://windows.microsoft.com/en-gb/windows-vista/learn-how-to-install-windows-vista-service-pack-2-sp2
-
For some reason there was never a iso of vista with sp2 put online, where as with Windows 7 MS has the ISOs available for download.
So you have to grab the 3 vista files
http://www.heidoc.net/joomla/technology-science/microsoft/57-windows-vista-direct-download-links
Then make an isp with it, THEN slipstream SP2 into it. Pain in the butt that is for sure lol
Shane
-
I uninstalled SP2, the KB2884256 update and the Dexcom driver failures still occurred. I got vlite (the program to create an updated installation disc) to run, but when trying to slipstream SP2 it stops working. Since removing SP2 did not help, I am not sure using an updated installation disc for repairs would help. I received a number of new updates. They all installed except for the problematic KB2884256.
-
I uninstalled SP2, the KB2884256 update and the Dexcom driver failures still occurred. I got vlite (the program to create an updated installation disc) to run, but when trying to slipstream SP2 it stops working. Since removing SP2 did not help, I am not sure using an updated installation disc for repairs would help. I received a number of new updates. They all installed except for the problematic KB2884256.
The idea was to avoid the problems with slipstreaming SP2 by creating a bootable SP1 disk from the previously linked article.
Create an external system image - uninstall SP2 then do the repair install using the Sp1 ISO and then reinstall SP2.
-
You want the disk to have SP2 no matter what. A repair install is basically doing an upgrade to the same version of Windows. Thats why you would normally need SP2 on the disk since you already have SP2 on the system and you cant upgrade backwards.
Not to mention the huge amount of bug fixes in SP2 is always good to have.
Shane
-
RE: Where is SP1?
SP1 (KB936330) came out Feb 4, 2008. My machine was built in August 2008. As best I can tell, all the dates on the files and folders on the Vista installation disc are November 2, 2006.
Except for the problematic USB security update, KB2884256, all other critical updates have properly installed.
The list of installed updates shows SP2 (KB948465), but not SP1. So what happened to SP1? If it is on the install disc, how can I verify it? If it is not there, what happened to it?
-
Tell you what, shoot me an email and I will see if there is a way for me to upload a vista sp2 iso to you. I dont mind doing it because its not a hacked version or anything, just a normal vista sp2 disk which I use when reinstalling vista, which I havent had to do in a long time lol
Its over 3 GB in size, so let me know :wink:
Shane
-
SOLVED
The Repair Install (http://www.vistax64.com/tutorials/88236-repair-install-vista.html) fixed things. It took over twelve hours to get everything working and up to date.
A problem occurred after the install, during Windows Setup, that that may have indicated a simple few minute fix for the orginal problems.
During Setup a box appeared on the screen saying "Setup has detected that Net Framework Version 4 needs to be repaired". The repair took a few minutes.
The Dexcom program uses Net Framework 4. I do not know if KB2884256 (security update for USB drivers) uses it. Is it possible a simple few minute repair could have fixed this, or was that a side issue?
I consider this problem solved. Thanks for all the help.
-
Very possible. But nothing told us that it was having trouble with .net at all. Any time there is a problem with .net I use a .net removal tool that gets rid of it completely and then I install .net fresh. Fixes it every time.
It is possible it was just another thing that was broken and you simply didnt know about it as well, hard to tell if they where tied together. :wink:
Shane