vista5456 my update work error code 80240018

since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

What happens when you restart the services?
If that does not help, you should ask in the appropriate private newsgroup since Build 5456 is not public available.
-- Jupiter Jones [MVP] http://www3.telus.net/dandemar http://www.dts-l.org
"FlamingoYao" wrote in message

since i stopped some of service,my update could not search for new updates. Error found:Code 80240018

Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message

since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message

Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:

Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message

The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

All of the versions I have been testing bring me to here from the desktop feedback -I set up on the connect site to get to the betanews.microsoft servers-I just come here to help out if I can.
"Colin Barnhorst" wrote:

Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

I'm techbeta too, but I subscribed to a couple of the Vista groups on msnews to help out and get a few laughs at the "How can I get my XP back?" posters. I always worry that some of my answers here actually only work with 5456. I'm not running 5384 any more.
"daddy3" wrote in message

All of the versions I have been testing bring me to here from the desktop feedback -I set up on the connect site to get to the betanews.microsoft servers-I just come here to help out if I can.
"Colin Barnhorst" wrote:
Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

I do think MS errored in using 5384 as CCP-after 2 weeks using it I felt it was going backwards from 5381 and almost reinstalled 5381 (I felt like I had egg on my face after telling everyone how good 5381 was and then they got to test 5384). I expected a different sku for CCP. I do like 5456 so far-it feels as good as 5381.
"Colin Barnhorst" wrote:

I'm techbeta too, but I subscribed to a couple of the Vista groups on msnews to help out and get a few laughs at the "How can I get my XP back?" posters. I always worry that some of my answers here actually only work with 5456. I'm not running 5384 any more.
"daddy3" wrote in message All of the versions I have been testing bring me to here from the desktop feedback -I set up on the connect site to get to the betanews.microsoft servers-I just come here to help out if I can.
"Colin Barnhorst" wrote:
Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

The folks here would love to have the flip3d icon in the quick launch bar. I was glad to see it show up again in 5456.
"daddy3" wrote in message

I do think MS errored in using 5384 as CCP-after 2 weeks using it I felt it was going backwards from 5381 and almost reinstalled 5381 (I felt like I had egg on my face after telling everyone how good 5381 was and then they got to test 5384). I expected a different sku for CCP. I do like 5456 so far-it feels as good as 5381.
"Colin Barnhorst" wrote:
I'm techbeta too, but I subscribed to a couple of the Vista groups on msnews to help out and get a few laughs at the "How can I get my XP back?" posters. I always worry that some of my answers here actually only work with 5456. I'm not running 5384 any more.
"daddy3" wrote in message All of the versions I have been testing bring me to here from the desktop feedback -I set up on the connect site to get to the betanews.microsoft servers-I just come here to help out if I can.
"Colin Barnhorst" wrote:
Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.

And the desktop icon to hide what you are looking at quick.
"Colin Barnhorst" wrote:

The folks here would love to have the flip3d icon in the quick launch bar. I was glad to see it show up again in 5456.
"daddy3" wrote in message I do think MS errored in using 5384 as CCP-after 2 weeks using it I felt it was going backwards from 5381 and almost reinstalled 5381 (I felt like I had egg on my face after telling everyone how good 5381 was and then they got to test 5384). I expected a different sku for CCP. I do like 5456 so far-it feels as good as 5381.
"Colin Barnhorst" wrote:
I'm techbeta too, but I subscribed to a couple of the Vista groups on msnews to help out and get a few laughs at the "How can I get my XP back?" posters. I always worry that some of my answers here actually only work with 5456. I'm not running 5384 any more.
"daddy3" wrote in message All of the versions I have been testing bring me to here from the desktop feedback -I set up on the connect site to get to the betanews.microsoft servers-I just come here to help out if I can.
"Colin Barnhorst" wrote:
Except that TechBeta doesn't work like that. There are not new TechBeta testers in the sense that there are new CPP testers. The TechBeta folks use the betanews.microsoft.com servers and not the msnews.microsoft.com servers.
"daddy3" wrote in message The link for newsgroups on the Beta desktop leads to the help and support page for Vista and then it links to here so that is why some new beta testers end up here and not on the private site.
"Colin Barnhorst" wrote:
Because this is a Vista ng. However, I too am puzzled about why he would not continue to use the private Vista newsgroups the TechBeta folks have been using for a year. Unless of course he has gotten a TechBeta copy improperly.
Having said that, this and the other public Vista newsgroups are not groups for beta testing. It just happens that that is all there is right now. In fact these are the public groups that will support Vista right through release and for years beyond. It is the Techbeta private groups that will shut down next year.
"Chad Harris" <Bushisamoron.net> wrote in message Mr. Flamingo--
As Jupiter says why would you try to deal with a private interim build 5456.5 Error on a public newsgroup when the 5% or less of Beta testers who do post on it post on a Beta newsgroup and there are something like 60 of them and one of these and ocassionally a Softie will grace the Beta group with their brief presence but almost never (once I've seen) here--unless you got 5456.5 via some kind of torrent before Brad Smith's homeboys and girls got to craft a brilliant and legally challenging and complex "Cease and Disist?"
Introduce yourself to the Beta groups and Connect's section if you have access to them where your needs can be better met.
It does remind me of my point about MSFT pointlessly witholding information about new features though as it encourages the unwashed masses to give them feedback with no feedback at all back to the unwashed masses and no info on features like the "Vista Restart Manager" from Product Managers Elsie Nallipogu and David Zipkin or Win RE or the half baked semblance of SFC that now exists in Vista that they could use.
CH
"FlamingoYao" wrote in message since i stopped some of service,my update could not search for new updates. Error found:Code 80240018.