Prev: Windows Update error 800B0100
Next: "windowsUpdate_800B0100" " WindowsUpdate_dt000"
From: olivin on 8 Sep 2009 15:09
Thanks Mr hnyman, this finally solved my problems!

"hnyman" wrote:

> F-Secure is admitting that there is a problem:
>
> The most recent info in their knowledge base is :
> Boot-loop issue in Windows Vista with F-Secure Internet Security and
> F-Secure Anti-Virus 2009/2010 - Aug 26, 2009
> http://www.f-secure.com/en_EMEA/support/knowledgebase/article-details.html?id=15004
> (http://www.f-secure.com/en_EMEA/support/knowledgebase/)
>
> Problem description
> When installing security updates for Windows Vista with SP2, the computer
> might continuously restart if the computer is running F-Secure Internet
> Security 2009/2010 or F-Secure Anti-Virus 2009/2010.
>
> Solution
> F-Secure has released a fix for this problem today, August 26, 2009.
> However, if you have already encountered this issue, you have to follow the
> instructions below to recover from the situation.
>
>
> "hnyman" <nomail(a)nomail.mm> wrote in message
> news:WEWhm.1690$La7.220(a)uutiset.elisa.fi...
> > PA Bear [MS MVP] wrote:
> >>> The combined antivirus/firewall suite is F-Secure Internet Security 2009
> >>
> >> And were all components of this suite (i.e., anti-virus; anti-spyware;
> >> firewall) enabled and running in the background when you installed SP2?
> >
> > Yes. the whole suite is installed and active, and was when SP2 was
> > applied.
> >
> > Earlier, during the past two years with Vista, there has been no problems
> > with windowsupdates and no interference from F-Secure.
> >
> > During the weekend I tested another PC I have access to, and also that
> > showed the same two errors: 8007000B and 80071A30. After two install
> > attempts it actually got into endless reboot loop, where is always started
> > boot with "configuring updates, stage 3/3" and then rebooted before
> > getting into Windows proper. System restore helped to recover from that.
> > Sounds similar like the problem here:
> > http://groups.google.fi/group/microsoft.public.windowsupdate/browse_thread/thread/1b82cf6dfccdec0f
> > )
> >
> > My own PC is self-built and installed, while the other one is HP laptop
> > with Vista Business pre-installed. Also that laptop has F-secure suite,
> > but otherwise there is not much common in software base.
> >
> > So, this seems not to be just a symptom of a singular PC, but might be
> > something else. Either incompatibility of some security software, or then
> > maybe there is actually something broken in Vista updates after SP2 is
> > applied.)
> >
> >> hnyman wrote:
> >>> PA Bear [MS MVP] wrote:
> >>>> What is your current anti-virus application? What third-party security
> >>>> applications are installed? What third-party firewall might be
> >>>> installed? The fact that one or more of these were running in the
> >>>> background when you installed SP2 may have caused the problem (sinsce
> >>>> you said the problems started after you'd installed SP2).
> >>>
> >>> The combined antivirus/firewall suite is F-Secure Internet Security
> >>> 2009, a
> >>> rather widely used program (at least in Europe). No other "third-party"
> >>> firewalls have ever been installed in the machine.
> >>>
> >>>> Start | In the search box, type WINVER and press ENTER: What Vista
> >>>> version is displayed here?
> >>>
> >>> Quite correctly: Version 6.0 (Build 6002: Service Pack 2)
> >>>
> >>> I noticed the symptoms first at the June monthly Microsoft update batch
> >>> after installing SP2, so I am guessing that it may be related to that,
> >>> but
> >>> I have no specific evidence about that.
> >>>
> >>>> hnyman wrote:
> >>>>> PA Bear [MS MVP] wrote:
> >>>>>> Did you install SP2 manually or via Windows Update?
> >>>>>
> >>>>> Manually.
> >>>>>
> >>>>>> Was your anti-virus application, any third-party security
> >>>>>> applications,
> >>>>>> and/or a third-party firewall running in the background when you
> >>>>>> installed SP2 (and/or IE8, if you installed it, too)?
> >>>>>
> >>>>> Yes. Like it has been during all the earlier Windows updates
> >>>>> (including
> >>>>> SP1)...
> >>>>>> Is your anti-virus application subscription current?
> >>>>>
> >>>>> Yes it is.
> >>>>>
> >>>>>> Has a(another) Norton or McAfee application ever been installed on
> >>>>>> this
> >>>>>> machine (e.g., a free-trial version that came preinstalled when you
> >>>>>> bought it)?
> >>>>>
> >>>>> No. Nothing else. I have installed everything from scratch by myself.
> >>>>> <paste> hnyman wrote:
> >>>>>> I have experienced problems with windowsupdate since three months
> >>>>>> (after
> >>>>>> installing Vista SP2). So far the symptom has mainly been error
> >>>>>> 8007000B.
> >>>>>> The newest monthly batch of Windows update again failed for me on
> >>>>>> first
> >>>>>> try
> >>>>>> on my Vista SP2 Ultimate 32.
> >>>>>> In addition to 8007000B there was now also error 80071A30
> >>>>>>
> >>>>>> WindowsUpdate.log shows the new errors, which make me think that
> >>>>>> somehow
> >>>>>> the file creation to "sandbox" fails:
> >>>>>> 2009-08-12 20:02:03:026 1332 34c DnldMgr ***********
> >>>>>> DnldMgr: New download job [UpdateId =
> >>>>>> {C03CD490-8035-41F9-B11E-23041508EFCA}.101] *********** 2009-08-12
> >>>>>> 20:02:03:042 1332 34c DnldMgr * Queueing update for
> >>>>>> download
> >>>>>> handler request generation. 2009-08-12 20:02:03:058 1332 34c
> >>>>>> DnldMgr Generating download request for update
> >>>>>> {C03CD490-8035-41F9-B11E-23041508EFCA}.101 2009-08-12 20:02:03:089
> >>>>>> 1332 34c Handler Generating request for CBS update
> >>>>>> C03CD490-8035-41F9-B11E-23041508EFCA in sandbox
> >>>>>> C:\Windows\SoftwareDistribution\Download\60a2d62269cb2dd06b814494b99209fe
> >>>>>>
> >>>>>> 2009-08-12 20:02:03:089 1332 34c Handler Selected
> >>>>>> payload
> >>>>>> type is ptExpress 2009-08-12 20:02:03:182 1332 34c
> >>>>>> Handler
> >>>>>> UH: DpxRestoreJob returned 0x80070002 2009-08-12 20:02:03:182 1332
> >>>>>> 34c Handler Detected download state is dsHavePackage 2009-08-12
> >>>>>> 20:02:12:246 1332 ce4 Handler FATAL: CBS called Error
> >>>>>> with
> >>>>>> 0x80071a30, 2009-08-12 20:02:12:246 1332 34c Handler
> >>>>>> FATAL:
> >>>>>> UH: 0x80071a30: Async stage operation failed in
> >>>>>> CUHCbsHandler::StageCbsPackage 2009-08-12 20:02:12:246 1332 34c
> >>>>>> Handler FATAL: Request generation for CBS update complete with
> >>>>>> hr=0x80071a30 and pfResetSandbox=0 2009-08-12 20:02:12:246 1332
> >>>>>> 34c Handler FATAL: Error source is 106. 2009-08-12 20:02:12:246
> >>>>>> 1332 34c DnldMgr FATAL:
> >>>>>> DM:CAgentDownloadManager::GenerateAllDownloadRequests:
> >>>>>> GenerateDownloadRequest failed with 0x80071a30. 2009-08-12
> >>>>>> 20:02:12:246
> >>>>>> 1332 34c DnldMgr Error 0x80071a30 occurred while downloading
> >>>>>> update; notifying dependent calls. 2009-08-12 20:02:12:917 1332
> >>>>>> 1650 AU >>## RESUMED ## AU: Download update [UpdateId =
> >>>>>> {FAE1F33B-4D16-44B6-851B-F864FB52E65C}] 2009-08-12 20:02:12:917
> >>>>>> 1332
> >>>>>> 1650 AU # WARNING: Download failed, error = 0x80071A30
> >>>>>> 2009-08-12
> >>>>>> 20:02:12:948 1332 1394 DnldMgr BITS job
> >>>>>> {F7153454-249F-4E9C-B66A-6F5120F5BF1C} completed successfully
> >>>>>> 2009-08-12
> >>>>>> 20:02:12:995 1332 1394 Misc Validating signature for
> >>>>>> C:\Windows\SoftwareDistribution\Download\f14ad06c449d646a06a1fdabee739a7a\Windows6.0-KB973540-x86-EXPRESS.cab:
> >>>>>>
> >>>>>> 2009-08-12 20:02:12:995 1332 1394 Misc Microsoft
> >>>>>> signed:
> >>>>>> Yes 2009-08-12 20:02:13:011 1332 1394 DnldMgr
> >>>>>> Download
> >>>>>> job
> >>>>>> bytes total = 9521749, bytes transferred = 111900
> >>>>>> During those seconds at between 20:02:03 and 20:02:12 there were the
> >>>>>> same
> >>>>>> "usual" errors in Event Log / system log as I have seen on previous
> >>>>>> months:
> >>>>>> * Event 1, source Kernel-Tm: "The Transaction
> >>>>>> (UOW={fe6f03ff-8101-11de-804b-00301bbc2e1b}, Description='') was
> >>>>>> unable to
> >>>>>> be committed, and instead rolled back; this was due to an error
> >>>>>> message
> >>>>>> returned by CLFS
> >>>>>> while attempting to write a Prepare or Commit record for the
> >>>>>> Transaction.
> >>>>>> The CLFS error returned was: 0xc01a002f." (The GUID there will
> >>>>>> change,
> >>>>>> but then "0xc01a002f" remains the same) * Event 136, source NTFS:
> >>>>>> "The
> >>>>>> default transaction resource manager on volume C: encountered an
> >>>>>> error
> >>>>>> while starting and its metadata was reset. The data contains the
> >>>>>> error
> >>>>>> code. * Event 136, source NTFS: "The default transaction resource
> >>>>>> manager
> >>>>>> on volume C: encountered an error while starting and its metadata was
> >>>>>> reset. The data contains the error code.
> >>>>>> After reboot (and following the advice in
> >>>>>> http://support.microsoft.com/kb/948252 ) the updates finally got
> >>>>>> installed
> >>>>>> on the next try.
> >>>>>> I am starting to suspect that this might be related to antivirus
> >>>>>> program
> >>>>>> (F-secure), as then have been some others who also have seen similar
> >>>>>> symptoms:
> >>>>>> http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/3ea8b7c2-4947-4cf4-b9c3-cdb59e739769
> >>>>>>
> >>>>>> http://www.pcadvisor.co.uk/forums/index.cfm?action=showthread&threadid=362250&forumid=1&sr=41
> >>>>>>
> >>>>>>
> >>>>>> ------
> >>>>>>
> >>>>>> Additional info:
> >>>>>>
> >>>>>> Previous month I experienced only the 8007000B error and noticed the
> >>>>>> three
> >>>>>> previously mentioned Event log errors, which seemed to pop up every
> >>>>>> now
> >>>>>> and
> >>>>>> then.
> >>>>>> Then I had trouble in getting the recommended (
> >>>>>> http://support.microsoft.com/kb/956699 ) command "FSUTIL resource
> >>>>>> setautoreset" to work on C: drive. It seemed to work for other
> >>>>>> drives, but
> >>>>>> for C: it complained about a missing Resource manager.
> >>>>>> Finally I found this info, which allowed me to clean the CLFS logs
> >>>>>> and
> >>>>>> then
> >>>>>> run the FSUTIL command (for C:\ ) after reboot:
> >>>>>> http://support.microsoft.com/kb/948252
> >>>>>> "Explanation: This problem occurs because, after the System Restore
> >>>>>> is
> >>>>>> performed, the Common Log File System (CLFS) transaction logs may be
> >>>>>> left
> >>>>>> in an inconsistent state. When the CLFS transaction logs are in an
> >>>>>> inconsistent state...
> >>>>>> To resolve this problem, delete the .blf files and the .regtrans-ms
> >>>>>> files
> >>>>>> from the %Windir%\System32\SMI\Store\Machine folder.
> >>>>>> After you restart the computer, the registry regenerates the deleted
> >>>>>> files.
> >>>>>> These regenerated files are in a consistent state." ----
> >>>>>>
> >>>>>> I am wondering that if this is something which should correct itself?
> >>>>>> Or is there something permanently wrong in Vista's bowels?
> >>>>>> Does it sound plausible that it might be the antivirus program
> >>>>>> causing
> >>>>>> something? Any other ideas about the cause?
> >>
>
>
>
 | 
Pages: 1
Prev: Windows Update error 800B0100
Next: "windowsUpdate_800B0100" " WindowsUpdate_dt000"