autorun.dll missing or corrupt

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have posted this question before and received one response. When I try to
install Windows Vista from the disk I purchased from Microsoft, I get the
following message: autorun.dll is missing or corrupt, cannot continue

I've seen two other postings and I am wandering if anyone has found the
solution. I am now trying to install it on a IBM with 1 gig of registered
ram and a 1.7 gig processor, with a 40 gig hard drive.
 
If you're having trouble with the disk you paid MSFT for, email them and
tell them to send you another--I believe I responded with a number of
solutions, or download the ISO and mount it using Virtual Server R2--you can
find it on the setup group under "A Major Problem" where I have given repeat
instructions on how to do this and links to Virtual Server R2 which can
mount the downloaded ISO without burning it.

If you paid them for a disc, and want a replacement email:

(e-mail address removed)
or (e-mail address removed)

These two individuals, employees at MSFT and developers claim they are
hungry for your feedback. By all means feed them now. They can make a
replacement DVD happen. They have plenty of DVDs for each build of the day
stacked on their desks. Tell them to compensate you with what they have
given TAP RC1 or Build 5487--they have DVDs of it or tell them to get you
one of the DVDs of RC1 they're getting ready to make public.

CH
 
Chad is correct in that we definitely want your feedback on Windows Vista,
be it the Beta 2 release or otherwise.

He's also correct in stating that you're much better off waiting until RC1
is released instead of requesting another copy of Beta 2, as our supply
channel has geared down from Beta 2 and is gearing up for RC1, so you'd be
unlikely to receive that version anyway. I'm sorry to state that that's the
case, but it's not something within my power to change.

Please, if you need a replacement DVD, check the Windows Vista blog
(http://blogs.technet.com/windowsvista/) or launch site
(http://www.microsoft.com/windowsvista/) when RC1 releases.

Regards,

-- Nick
 
As Nick has stated, we do want your feedback on Vista. However, I'm not a
member of the Vista team, and I don't have any control of how or when DVDs
are distributed. I don't have stacks of DVDs on my desk- in fact, I only use
builds the public has access to already. :)

See Nick White's post in this thread as well, if you haven't already. In my
position, I'm concerned with feedback- in the sense that I work to help
connect Microsoft product teams with their customers so the people who can
actually do something about the feedback have the tools to do so. Feedback
is critical to our success. It's especially critical that it go to the right
places, which is what I help with.

Thanks and regards,
 
As Nick has stated, we do want your feedback on Vista. However, I'm not a
member of the Vista team, and I don't have any control of how or when DVDs
are distributed. I don't have stacks of DVDs on my desk- in fact, I only use
builds the public has access to already. :)

See Nick White's post in this thread as well, if you haven't already. In my
position, I'm concerned with feedback- in the sense that I work to help
connect Microsoft product teams with their customers so the people who can
actually do something about the feedback have the tools to do so. Feedback
is critical to our success. It's especially critical that it go to the right
places, which is what I help with.

Thanks and regards,
 
Why Corey--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been in a one stop shop
searchable place

Why doesn't the public who I believe is getting a couple builds as a primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
Why Nick--

1) Aren't the bugs' categories that Paul Donnelly has massaged 50 million
ways to Christmas for distribution to the appropriate developers, team
members and PMs, since you all have access to cluster servers and SQL and
all of MSFT's expertise can be brought to bear in sorting them haven't you
posted the categories of bugs and their contexts like

1) Fixed in Build
2) Will definitely be fixed in a future build or SP whatever
3) We won't fix until perhaps Vienna Blackcomb or never

so that the public can see what the bugs have been and continue to be in a
one stop shop searchable place on Connect just as the TBTs can? Why freeze
out the public in so many respects? There is no harm into distributing this
knowledge. The Gates Foundation has a big educational component. The Beta
for Vista denies information in a very harmful way toward Vista learning
curves. The technical writers on the Vista team have dragged in getting
info onto MSDN or Technet and the Product Guide is very very superfiical
sometimes giving important topics like Desmond Lee's teams' Win RE a couple
sentences. There is very little on Win RE on the Web--I include nearly all
the links when I post to help someone fix Vista that exist unless they add
nothing more to the info on my links as it is now.

Win RE btw is not working nearly as consistently as a Repair Install in XP
does. Auto Repair for apps and utilities and components of Vista
themselves is a good idea, but it fails much of the time.

Why doesn't the public who I believe is getting a couple builds as a primary
**marketing** i.e. sales tool have the same access to bug reports as
TBTs--why the "considering it"--it should be a no brainer.

Why deny the public access to the Vista Beta chats so that they can get
information on using Vista and a little of the information they are denied
by not having access to the bug info on Connect?

Why deny the public access to the Vista Live meetings?

What in the world is the downside and the harm to MSFT or anyone else not to
share this info.

There is scant information on MSFT's site now on several key topics,
features, and components within Vista.

CH
 
leo said:
I have posted this question before and received one response. When I try to
install Windows Vista from the disk I purchased from Microsoft, I get the
following message: autorun.dll is missing or corrupt, cannot continue

I've seen two other postings and I am wandering if anyone has found the
solution. I am now trying to install it on a IBM with 1 gig of registered
ram and a 1.7 gig processor, with a 40 gig hard drive.
Click to expand...
 
Back
Top