I have been receiving a code 8007000B error and cannot update at all. Does
anyone have any suggestions.
I have been receiving a code 8007000B error and cannot update at all. Does
anyone have any suggestions.
Which version of Windows are you using?
If it is windows vista and you are seeing this error when trying to install
updates, please try the following
1. Open an Administrator command prompt by right clicking on Start -> All
Programs -> Accessories -> Command Prompt and selecting "Run as
Administrator" and clicking "Allow" for the elevation prompt
2. In the command prompt, type the command below
fsutil resource setautoreset true C:\
(This assumes that C: is the drive in which Vista is installed. If it is
installed on another drive like D:, please change the drive letter
appropriately)
3. Reboot the machine
This is the resolution only for 8007000b error while installing updates on
Vista. This doesn't apply for other OS like Windows XP SP2 etc
If your OS is not Vista, please send C:\windows\windowsupdate.log
I tried the setautoreset solution and also received an error message that the
'file or directory is corrupted.."
Is there a recommendation on what to try next?
I solved the error in this way:
1)Boot Vista from DVD,
2)Click to rapair installation (or something like that)
2)Run prompt command
3)start chkdsk /f in the volume where is installed Vista
Then restart Vista from HD and try to update
It works form me!
Thanks. I had tried chkdsk /r from my normal login with no luck. I put the
Driver/Utilities Dell CD in the system and booted from it by hitting F12. I
ran a full disk diagnostics - everything passed (it took half a day to run
btw). Upon reboot - I missed hitting F12 quick enough and Windows started to
load - so I thought I could just turn off the system and retry. No luck - it
said Windows had problems and was going to recover and something about if the
disk was involved - it could take a long time. So - I let it recover and
went shopping. When it finished - I successfully ran the fsutil command
mentioned in the thread here and then successfully ran the windows update.
Thanks to all who have helped.
Now if I could figure out why the system still runs slow I'll be in great
shape.
Not only am I having the 8007000B error which won't allow me to update, I am
also unable to update my Trend Antivirus or add lots of very easy to install
software such as Adobe Reader.
I thought it must be a hard drive problem, so I took it to geek squad for
warranty repair. They say it's a software problem, likely Vista, and wanted
to charge me $200 to fix it.
my laptop is pretty new, so I decided to wipe it clean with the recovery CD.
I got a message indicating a hard drive error, but it did go ahead and load
Vista. I reinstalled all my software, but I still get the above error and
cant update Trend Antivirus or install Adobe Reader.
hi please could you help i.ve been tring to do what you say but i'm not that
smart on the pc i go into start b ut i cant find run as Administrator so i
cant go any further pease reply thanks
I've been having the same trouble as the error listed (8007000B) below when
doing 'Windows Update' for my Vita operating system, but when I follow the
instructions listed I have the return message "The operation completed
successfully" then I reboot and then run 'Windows Update' but I still get the
same error.
Do you have any other suggestions?
By now 'Command Prompt' should be appearing inyour recently used programme
list. click on 'Start>then in the list above you should have 'Command Prompt'
highlight the progamme but now right click it then in the new list of option
there should be one that states "run as administrator" then click this.
Cheers, hope it helps you more than it helped me.
hi i have done all that i was told ie command promp but still cant get the
updtes to download also just realised that when i went to put a new cd in
the drive to copy on to the pc it wont work could this have anything to do
with each other so looking for answers to cure that problem to my pc is
windows vista home adition please help thanks
Thanks SUDHEER GN (MSFT) I had error 8007000B and could not update, run
defragmentor or install pinnacle studio 11. After following your advice, all
of my problems are over. Many Thanks
hi chris thanks for trying to help but no joy still cant download alos just
noticed anoth problem tryed putting a cd in the drive to list to but that
doesnt seem to work does the two have anything in common trying to sort out
two things now really not happy i'm useing vista windows love to have so
more ideas
I am having trouble finding the "Run as Administrator" option. The user
accounts state that I am an administrator, but your fix does not acknowledge
my status.
Thank you so much Ferra1980...wherever/whoever you are, you have great skill
in concise technical writing and I wish you the utmost success in computing
with vista!
....just one thing...when you boot vista from the disk, then choose to
"repair installation" then use the cmd program to change directory to C:\ (cd
C:\) (assuming C:\ is the drive where vista is installed)...before "chkdsk
/f" will start to run it will ask you to release all handles currently
pointing to this disk...i have found that doing this seems to leave
everything okay!
Thank Goodness for this post. Cleared up my problem with failed vista
updates right away, although I did have to run the command prompt in safe
mode because I got "you must be the administrator" error in regular startup.
I followed these steps, but when I typed in the command into command prompt,
I get this error:
Error: The system cannot find the file specified.
Any ideas? Anyone?
Are you running Vista?
Windows Update error 8007000b
http://windowshelp.microsoft.com/Win...904121033.mspx
I'm making this post to help any of those that might get this in the future.
It took me a few times of googling to find a fix that actually worked. Anyway
here it is:
If you are updating Windows Vista and get Error # 8007000B (and error given
when Windows can't update) it recommends you do this:
Go to the Command Prompt (make sure to right click and run as administrator)
then type: fsutil resoruce setautoreset true C:\
This is suppose to fix the Windows updater in Windows, but in my case it
errored saying no specific file found
So after messing with the fsutil resource commands in DOS I found this out:
"Transaction support within the specified file system resource manager is
not started or was shut down due to an error"
So I googled this of course and finally got some help.
Below is a link to a Microsoft fix to this problem
http://support.microsoft.com/kb/939615
Click on the fix and run it. After you reboot, you will be able to get your
updates.
For me the Windows Update error 8007000B has started to surface after
installing the Vista SP2. It is now surfacing in three different PCs:
One Shuttle PC running Vista Ultimate (English) and two HP 6830S laptops
running Vista Business (English and Finnish).
So, I think that the error is not that much related to individual PC,
but that there is something wrong in Windows Update behaviour after
Vista SP2.
When the error materializes, there is no Task Scheduler (and thus also
no shadow copies etc.)
Looking in <services.exe> and opening task scheduler (which was set to
auto) and all the options are greyed out.
When looking to the event log, I find in the System section the
following entries which seem to have started after I installed Vista SP2:
There are the following events:
* 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.: C:
1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0"
* 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.
1C000400020030000200000088000480000000002B001AC0000000000000000000000000000000002B001AC0"
* 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.
1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0"
(The same error code as in the first message)
The first of those errors comes first/separately. The other three seem
to surface at the same time.
The events match the already mentioned problems with the "Transaction
support..."
I have no clue, what those errors actually mean. Disk failure? Not
likely, as I have noticed nothing towards that. Somehow, something about
the NTFS gets disabled/corrupted and that prevents task scheduler from
working.
As the same update errors have surfaced for me now in three different
computers, I do not believe that it is a hardware related problem, but
something else. My prime suspect is still something connected to SP2.
Additional info:
I had trouble in getting the FSUTIL resource setautoreset command 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
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.
----
Curiously, that KB article 948252 references
http://support.microsoft.com/default.aspx/kb/939399/ , which KB leads to
the same FixIt solution 50140 as KB 956699 and 939615.
http://support.microsoft.com/kb/939615
http://support.microsoft.com/kb/956699
However, the manual commands given in the article 948252 are different,
and they finally helped me to get the FSUTIL command to work.
Still some more info:
I started to ponder about the Task Scheduler issue, as that annoyed me.
Trying to look into Task scheduler always produced errors about Google
Updater. Something like "The task image is corrupt or has been tampered
with.Google Software Updater".
There is even a thread about that error:
http://social.answers.microsoft.com/...6-d908d476db11
Then I also noticed that in Event log (System), the next error after the
three NTFS/Kernel-TM errors usually was "The Google Software Updater
service entered the stopped state."
And In Task Scheduler's logs (Event Log / Applications and Services logs
/ Microsoft / Windows / TaskScheduler / Operational ) there are errors
like: 706 'Task Compatibility module failed to update task
"GoogleUpdateTaskMachine.job" to the required status 3. Additional
Data: Error Value: 2147942402.'
So maybe there is something wrong with current setup of Google's updater
in my Pc.
After some Task scheduler editing and REGEDIT usage, I managed to remove
the Google Updater related tasks from Task scheduler. The error
disappeared and right now the system has performed normal scheduled
tasks (like Shadow copies etc.) normally.
I have only Google Earth installed, nothing else. Updating that has
required the updater, But I have had no Google toolbar or desktop or
Chrome ever installed.
So, I am thinking that maybe the underlying reason for the 8007000B
error and Task Scheduler errors might be some kind incompatibility of
GoogleUpdater and Vista SP2 installation. (Because there was Google
Updater already before I installed SP2.)
Hopefully that might be a cure, but only the time (and next updates)
will show that.
Well, after fixing Google updater, the same error materialized also for
'mcupdate' service (the Media Center updater service). So, Google was
not the final reason.
Next idea:
I noticed that I have a repeating "Windows Search" related error in
Event Log / Application:
Event 3013
Source Search
Task category Gatherer
The entry <C:\USERS\XXXXXX\APPDATA\ROAMING\ZZZZZz\CCCC.CCC> in the hash
map cannot be updated.
Context: Application, SystemIndex Catalog
Details: A device attached to the system is not functioning. (
0x8007001f )
The error was there several times, maybe once per day. Regarding always
the same file, which functioned just normally and was read/written
several times per day.
I was able to cause the previously mentioned Kernel-Tm error just by
clicking the "Event Log Online Help" link in event log page for that
search error. Clicking that link and accepting "send information" dialog
did not lead to an web page opening. Instead the errors (Kernel-Tm and
NTFS) materialized to the event log.
So I started to think that maybe there is something wrong with the inxed
created ny the new Windows Search 4.0 (or whatever).
I then decided to clean the Windows Search / indexing database. Opened
the control panel for Indexing options and from Advanced options the
"Restore defaults", which will cause the index to be rebuilt. After
reboot, again no errors after that, but lets see what happens.
I am still not sure that I have found any final reason for the 8007000B
error...
Despite various solutions offered and countless hours spent trying to update
my Vista machine.... my advice is don't knock yourself out trying. As time
goes by, error messages just seem to keep increasing along with frustration.
Hi Sir,
I have tried the method as mentioned by you,
1. Open an Administrator command prompt by right clicking on Start -> All
Programs -> Accessories -> Command Prompt and selecting "Run as
Administrator" and clicking "Allow" for the elevation prompt
2. In the command prompt, type the command below
fsutil resource setautoreset true C:\
(This assumes that C: is the drive in which Vista is installed. If it is
installed on another drive like D:, please change the drive letter
appropriately)
3. Reboot the machine
However, same problem still persists, the problem whereby the download
doesnt start and it says windows cant check for updates, etc. So is there
like any other solutions to this problem cause it has been bothering me for a
real long time.
Posting Permissions
Reply With Quote
Bookmarks