(cross-post added to Vista Perf & Maint)
"Stymied Jack" Stymied wrote in message
...
I can't get any info on this error code, perhaps someone out there can help.
I haven't been able to update my Vista32 for several weeks...first there is a
message saying I need to install an update to my updates, so I can update
(??) then I give it the OK to do that and I get an error code 8007010b. i
haven't been able to find a thing about that error code and have been unable
to install the Vista SP or anything else.


See the answers I gave to "Nellypledge" in March?
Yours is even easier:

cmd_output OS="XPsp2"
E:\set /a c = 0x10B
267
E:\net helpmsg %c%

The directory name is invalid.
/cmd_output

So, in order to find out *what* "directory name is invalid"
you are going to have to search your log files for some context,
either with the hex code or its decimal equivalent.


Good luck

Robert Aldwinckle
---

Robert-
I appreciate the response, but I can't make heads or tails of it! I am not
wise in the ways of the workings of this computer. If it wouldn't be too much
trouble, could you translate what you wrote for me?
Thanks again for your time, JB

"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"Stymied Jack" Stymied wrote in message
...
I can't get any info on this error code, perhaps someone out there can help.
I haven't been able to update my Vista32 for several weeks...first there is a
message saying I need to install an update to my updates, so I can update
(??) then I give it the OK to do that and I get an error code 8007010b. i
haven't been able to find a thing about that error code and have been unable
to install the Vista SP or anything else.


See the answers I gave to "Nellypledge" in March?
Yours is even easier:

cmd_output OS="XPsp2"
E:\set /a c = 0x10B
267
E:\net helpmsg %c%

The directory name is invalid.
/cmd_output

So, in order to find out *what* "directory name is invalid"
you are going to have to search your log files for some context,
either with the hex code or its decimal equivalent.


Good luck

Robert Aldwinckle
---

"Stymied Jack" wrote in message
...
Robert-
I appreciate the response, but I can't make heads or tails of it! I am not
wise in the ways of the workings of this computer. If it wouldn't be too much
trouble, could you translate what you wrote for me?


I give hints which I expect posters who need help will try to use
to supplement their own searches and analyses.

So, I showed you what your code may mean, and that there is insufficient
detail provided by the code to provide any specific advice other than
to look for some context in your logs, e.g. search your harddrive(s) for
all files which contain that code which were written to by the update.

In fact, such a specific search is not possible but what is possible is to
search for files which contain the string, which were created or changed
on the day that you ran the update; then sort the results list by Date Modified;
then scroll to the minutes when the update was run. Chances are that
there are only a few files which will be found which fit all those criteria,
so then to examine them all you need to do is drag them one at a time
to an open Notepad window and do finds in there.


If you are "stymied" that implies that you have tried something.
So, if you tried something tell us what it was and what your results were.


HTH

Robert
---


Thanks again for your time, JB

"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"Stymied Jack" Stymied wrote in message
...
I can't get any info on this error code, perhaps someone out there can help.
I haven't been able to update my Vista32 for several weeks...first there is a
message saying I need to install an update to my updates, so I can update
(??) then I give it the OK to do that and I get an error code 8007010b. i
haven't been able to find a thing about that error code and have been unable
to install the Vista SP or anything else.


See the answers I gave to "Nellypledge" in March?
Yours is even easier:

cmd_output OS="XPsp2"
E:\set /a c = 0x10B
267
E:\net helpmsg %c%

The directory name is invalid.
/cmd_output

So, in order to find out *what* "directory name is invalid"
you are going to have to search your log files for some context,
either with the hex code or its decimal equivalent.


Good luck

Robert Aldwinckle
---

Again, Robert, thanks for your time in responding.

I noticed the problem when I tried to install a game...there was an
incomplete installation and, when looking for a reason, stumbled across the
fact that windows update had not been updating automatically for several
weeks. So I ran a manual update and got a message that read something like,
"In order to update, you need to install something or other for the update
itself...would you like to do this?" I, of course, would like that so I
clicked install. It spent around 60 seconds working and then I get the error
code 8007010B. Searching the trouble shooting guide did not help (other than
directing me to these posts). I gave up after several attempts last month and
was resigned to the fact that I would have to get a pro over.

I was surprised the other night, when shutting down, to see the computer
prompt, "Install updates, then shutdown?" So I checked back and went through
the update history and saw that several updates DID get installed, while
several "failed". Going back through my history with the computer (02/07) I
saw several "failed" messages- probably 85%.

Since seeing your responses I have asked others (who are wiser in the ways
of the works of the computer) to translate. I still don't know what it is
your suggesting...I am clueless when it comes to "codes" and such....how do I
search my hard drive for these things? I may be too hopeless to have this
solved on these posts...

Thanks again Robert, for your time. JB

"Robert Aldwinckle" wrote:

"Stymied Jack" wrote in message
...
Robert-
I appreciate the response, but I can't make heads or tails of it! I am not
wise in the ways of the workings of this computer. If it wouldn't be too much
trouble, could you translate what you wrote for me?


I give hints which I expect posters who need help will try to use
to supplement their own searches and analyses.

So, I showed you what your code may mean, and that there is insufficient
detail provided by the code to provide any specific advice other than
to look for some context in your logs, e.g. search your harddrive(s) for
all files which contain that code which were written to by the update.

In fact, such a specific search is not possible but what is possible is to
search for files which contain the string, which were created or changed
on the day that you ran the update; then sort the results list by Date Modified;
then scroll to the minutes when the update was run. Chances are that
there are only a few files which will be found which fit all those criteria,
so then to examine them all you need to do is drag them one at a time
to an open Notepad window and do finds in there.


If you are "stymied" that implies that you have tried something.
So, if you tried something tell us what it was and what your results were.


HTH

Robert
---


Thanks again for your time, JB

"Robert Aldwinckle" wrote:

(cross-post added to Vista Perf & Maint)
"Stymied Jack" Stymied wrote in message
...
I can't get any info on this error code, perhaps someone out there can help.
I haven't been able to update my Vista32 for several weeks...first there is a
message saying I need to install an update to my updates, so I can update
(??) then I give it the OK to do that and I get an error code 8007010b. i
haven't been able to find a thing about that error code and have been unable
to install the Vista SP or anything else.


See the answers I gave to "Nellypledge" in March?
Yours is even easier:

cmd_output OS="XPsp2"
E:\set /a c = 0x10B
267
E:\net helpmsg %c%

The directory name is invalid.
/cmd_output

So, in order to find out *what* "directory name is invalid"
you are going to have to search your log files for some context,
either with the hex code or its decimal equivalent.


Good luck

Robert Aldwinckle
---