On build 5384 upgrading to RC1, the upgrade compatibility check incorrectly
reports that McAfee Internet Security and McAfee firewall are installed and
are not compatible. It requires me to remove them so it only exits the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it hasn't
ever been installed. I search the machine for mcafee as well as the registry
just to see if there was anything referencing the McAfee software and there
isn't a reference anywhere, but clearly the upgrade advisor see something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of the
upgrade advisor's incorrect assessment of the software on the machine?

I don't know Jeff. But you can use AVAST though 5472. Starting with 5536
pre-RC1 and RC1 I found Avast needs a workaround to install which is to
uncheck driver inspection of Avast's software drivers typing "verifier" in
the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it works
perfectly. I understand you are comfortable with McAfee but right now to
enjoy the Beta try using Trend until the companies sort things out toward
RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are installed
and
are not compatible. It requires me to remove them so it only exits the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of the
upgrade advisor's incorrect assessment of the software on the machine?

Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like ya
said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with 5536
pre-RC1 and RC1 I found Avast needs a workaround to install which is to
uncheck driver inspection of Avast's software drivers typing "verifier" in
the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it
works perfectly. I understand you are comfortable with McAfee but right
now to enjoy the Beta try using Trend until the companies sort things out
toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are installed
and
are not compatible. It requires me to remove them so it only exits the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of the
upgrade advisor's incorrect assessment of the software on the machine?

I am not 100% that it will get it in--my experience though is that it can.
Without it what happened is that you could run a scan with AVAST (1/2 the
equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the AV
entry and uncheck all the software drivers listed for "inspection" by
verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program of
your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that this
will prevent some BSOD stop errors in Vista and XP I've seen that have a
"we've shut down the OS because of a corrupt kernel stack driver." The
problem is though, which one since if you put driverquery in the run box,
you get a list of anywhere from 130 and up kernel stack drivers (software
and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will tell
you then on 5472 and up that it won't turn on the AV protection. It will
run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you install
it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps you
take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier Is
Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like ya
said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which is
to uncheck driver inspection of Avast's software drivers typing "verifier"
in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it
works perfectly. I understand you are comfortable with McAfee but right
now to enjoy the Beta try using Trend until the companies sort things out
toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are installed
and
are not compatible. It requires me to remove them so it only exits the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of the
upgrade advisor's incorrect assessment of the software on the machine?

Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was installed
but that antivirus has never been installed. That sounds wrong so I hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some Driver
Verifier information got added into the mix too. Why are these related to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff didn't
seem concerned about these other two AV products and there are no Driver
Verifier settings present on a system unless someone (Jeff) created these
settings for some reason.

But it is very possible that I missed something - please clarify if that is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it can.
Without it what happened is that you could run a scan with AVAST (1/2 the
equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the AV
entry and uncheck all the software drivers listed for "inspection" by
verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program of
your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack driver."
The problem is though, which one since if you put driverquery in the run
box, you get a list of anywhere from 130 and up kernel stack drivers
(software and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will
tell you then on 5472 and up that it won't turn on the AV protection. It
will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB
below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps you
take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier Is
Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like ya
said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which is
to uncheck driver inspection of Avast's software drivers typing
"verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it
works perfectly. I understand you are comfortable with McAfee but right
now to enjoy the Beta try using Trend until the companies sort things
out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are installed
and
are not compatible. It requires me to remove them so it only exits the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of
the
upgrade advisor's incorrect assessment of the software on the machine?

Dan,
O.K.
#1 there are 2 Jeff's here. The 1st post is different;then my post.
I was responding to Chad about Avast; being fully able to run-pre-5536
and now; being denied for incompatabilty in the rc1 tree.
Which Avast themselves;e-mailed me and stated it was an MSFT issue in 5536;
that they were assured ; by MSFT themselves; that the issue would be fixed
in subsequent builds. Which;apparently; has not been addressed in 5600.
Avast now runs scan only;but for all other features;ie shell
integration;web scan;e-mail protection etc. ; vista now reports blocking due
to driver incompatabilty. Further simple investigation of these features
being blocked;is that Avast is getting an RPC error.
And; to further the fact;as Chad has pointed out numerous times; public
feedback;through Connect;may be seen by you guys;but we have no recourse to
see the actions taken. Complicating the issue further; I'm no engineer;and
didn't even realize verifier.exe was there. If there is a workaround;using
verifier.exe; I'm going forward;not waiting for a patent- this is is
resolved/removed; from Connect;with no ability to even see the results of
bugs posted;because I am not in the private beta.
I hope this clarifies the situation. Two different Jeff's
Jeff
"Dan Mihai [MSFT]" wrote in message
...
Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was
installed
but that antivirus has never been installed. That sounds wrong so I hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some
Driver
Verifier information got added into the mix too. Why are these related to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff didn't
seem concerned about these other two AV products and there are no Driver
Verifier settings present on a system unless someone (Jeff) created these
settings for some reason.

But it is very possible that I missed something - please clarify if that
is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it can.
Without it what happened is that you could run a scan with AVAST (1/2 the
equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the AV
entry and uncheck all the software drivers listed for "inspection" by
verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program
of your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack driver."
The problem is though, which one since if you put driverquery in the run
box, you get a list of anywhere from 130 and up kernel stack drivers
(software and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will
tell you then on 5472 and up that it won't turn on the AV protection. It
will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB
below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps you
take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier
Is Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like ya
said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which
is to uncheck driver inspection of Avast's software drivers typing
"verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it
works perfectly. I understand you are comfortable with McAfee but
right now to enjoy the Beta try using Trend until the companies sort
things out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are
installed and
are not compatible. It requires me to remove them so it only exits
the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of
the
upgrade advisor's incorrect assessment of the software on the machine?

Indeed, I didn't realize that there were two different Jeff's and they were
discussing about two separate problems in the same thread. :-) Thanks for
the clarification!

I hope this helps: I am aware of the Avast incompatibility with build 5600.
I will try to find someone who has been working on that issue and ask them
to get back to you with the latest status. As far as I know it is not
related to Driver Verifier though, so I recommend not trying to use
verifier.exe in any way for this particular issue.

Dan

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Jeff" wrote in message
...
Dan,
O.K.
#1 there are 2 Jeff's here. The 1st post is different;then my post.
I was responding to Chad about Avast; being fully able to run-pre-5536
and now; being denied for incompatabilty in the rc1 tree.
Which Avast themselves;e-mailed me and stated it was an MSFT issue in
5536; that they were assured ; by MSFT themselves; that the issue would be
fixed in subsequent builds. Which;apparently; has not been addressed in
5600.
Avast now runs scan only;but for all other features;ie shell
integration;web scan;e-mail protection etc. ; vista now reports blocking
due to driver incompatabilty. Further simple investigation of these
features being blocked;is that Avast is getting an RPC error.
And; to further the fact;as Chad has pointed out numerous times; public
feedback;through Connect;may be seen by you guys;but we have no recourse
to see the actions taken. Complicating the issue further; I'm no
engineer;and didn't even realize verifier.exe was there. If there is a
workaround;using verifier.exe; I'm going forward;not waiting for a patent-
this is is resolved/removed; from Connect;with no ability to even see the
results of bugs posted;because I am not in the private beta.
I hope this clarifies the situation. Two different Jeff's
Jeff
"Dan Mihai [MSFT]" wrote in message
...
Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was
installed
but that antivirus has never been installed. That sounds wrong so I hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some
Driver
Verifier information got added into the mix too. Why are these related to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff
didn't
seem concerned about these other two AV products and there are no Driver
Verifier settings present on a system unless someone (Jeff) created these
settings for some reason.

But it is very possible that I missed something - please clarify if that
is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it
can. Without it what happened is that you could run a scan with AVAST
(1/2 the equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the
AV entry and uncheck all the software drivers listed for "inspection" by
verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program
of your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack
driver." The problem is though, which one since if you put driverquery
in the run box, you get a list of anywhere from 130 and up kernel stack
drivers (software and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will
tell you then on 5472 and up that it won't turn on the AV protection.
It will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB
below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps
you take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier
Is Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like
ya said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which
is to uncheck driver inspection of Avast's software drivers typing
"verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and it
works perfectly. I understand you are comfortable with McAfee but
right now to enjoy the Beta try using Trend until the companies sort
things out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are
installed and
are not compatible. It requires me to remove them so it only exits
the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software and
there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of
the
upgrade advisor's incorrect assessment of the software on the
machine?

Dan;
No problem;
I've been trying to help all along;from 5384 thru 5600; and ;not to say it's
MINE;but; I've used my real name-Jeff-tp post in Ng's for a very long time.
Is quite frustrating however;to be denied access to bug reports filed on
Connect;legitimate concerns;to try to help you guys; and getting a
patent-brush off; when I try to see the bug I posted; because I'm not in the
private Beta.
It would be great to have someone get back to me.
Jeff

"Dan Mihai [MSFT]" ,com wrote in message
...
Indeed, I didn't realize that there were two different Jeff's and they
were discussing about two separate problems in the same thread. :-) Thanks
for the clarification!

I hope this helps: I am aware of the Avast incompatibility with build
5600. I will try to find someone who has been working on that issue and
ask them to get back to you with the latest status. As far as I know it is
not related to Driver Verifier though, so I recommend not trying to use
verifier.exe in any way for this particular issue.

Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Jeff" wrote in message
...
Dan,
O.K.
#1 there are 2 Jeff's here. The 1st post is different;then my post.
I was responding to Chad about Avast; being fully able to run-pre-5536
and now; being denied for incompatabilty in the rc1 tree.
Which Avast themselves;e-mailed me and stated it was an MSFT issue in
5536; that they were assured ; by MSFT themselves; that the issue would
be fixed in subsequent builds. Which;apparently; has not been addressed
in 5600.
Avast now runs scan only;but for all other features;ie shell
integration;web scan;e-mail protection etc. ; vista now reports blocking
due to driver incompatabilty. Further simple investigation of these
features being blocked;is that Avast is getting an RPC error.
And; to further the fact;as Chad has pointed out numerous times;
public feedback;through Connect;may be seen by you guys;but we have no
recourse to see the actions taken. Complicating the issue further; I'm no
engineer;and didn't even realize verifier.exe was there. If there is a
workaround;using verifier.exe; I'm going forward;not waiting for a
patent- this is is resolved/removed; from Connect;with no ability to even
see the results of bugs posted;because I am not in the private beta.
I hope this clarifies the situation. Two different Jeff's
Jeff
"Dan Mihai [MSFT]" wrote in message
...
Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was
installed
but that antivirus has never been installed. That sounds wrong so I hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some
Driver
Verifier information got added into the mix too. Why are these related
to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff
didn't
seem concerned about these other two AV products and there are no Driver
Verifier settings present on a system unless someone (Jeff) created
these
settings for some reason.

But it is very possible that I missed something - please clarify if that
is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it
can. Without it what happened is that you could run a scan with AVAST
(1/2 the equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the
AV entry and uncheck all the software drivers listed for "inspection"
by verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program
of your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack
driver." The problem is though, which one since if you put driverquery
in the run box, you get a list of anywhere from 130 and up kernel stack
drivers (software and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will
tell you then on 5472 and up that it won't turn on the AV protection.
It will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB
below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps
you take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier
Is Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like
ya said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which
is to uncheck driver inspection of Avast's software drivers typing
"verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and
it works perfectly. I understand you are comfortable with McAfee but
right now to enjoy the Beta try using Trend until the companies sort
things out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are
installed and
are not compatible. It requires me to remove them so it only exits
the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software
and there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of
the
upgrade advisor's incorrect assessment of the software on the
machine?

Dan;
Sorry to bother you;but since I've got someone who is being helpful;
maybe you can have someone look into this;also;
Getting a power BSOD on Dell e1505 w/Intel core duo T2500 whenever I
unplug from ac power.
Starting with the rc1 branch build 5536;and subsequent builds;including
RC1;a MAJOR ACPI power BSOD whenever this laptop is unplugged from ac
power.

To research this; I uninstalled/reformatted and installed various o.s.'s. No
problems.
this includes XP; Linux; and PRE-RC1 tree;builds. Build 5384/Beta 2 ; build
5472; do not exhibit this behavior; they in fact;work great.
This has also been sent via WER; and also through feedback; a HUGE issue
for me.
Any help would be greatly appreciated;and you can reach me directly at

This is MAJOR for me; if not resolved;can't run Vista at RTM.
Thanks Again,

Jeff


"Dan Mihai [MSFT]" ,com wrote in message
...
Indeed, I didn't realize that there were two different Jeff's and they
were discussing about two separate problems in the same thread. :-) Thanks
for the clarification!

I hope this helps: I am aware of the Avast incompatibility with build
5600. I will try to find someone who has been working on that issue and
ask them to get back to you with the latest status. As far as I know it is
not related to Driver Verifier though, so I recommend not trying to use
verifier.exe in any way for this particular issue.

Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Jeff" wrote in message
...
Dan,
O.K.
#1 there are 2 Jeff's here. The 1st post is different;then my post.
I was responding to Chad about Avast; being fully able to run-pre-5536
and now; being denied for incompatabilty in the rc1 tree.
Which Avast themselves;e-mailed me and stated it was an MSFT issue in
5536; that they were assured ; by MSFT themselves; that the issue would
be fixed in subsequent builds. Which;apparently; has not been addressed
in 5600.
Avast now runs scan only;but for all other features;ie shell
integration;web scan;e-mail protection etc. ; vista now reports blocking
due to driver incompatabilty. Further simple investigation of these
features being blocked;is that Avast is getting an RPC error.
And; to further the fact;as Chad has pointed out numerous times;
public feedback;through Connect;may be seen by you guys;but we have no
recourse to see the actions taken. Complicating the issue further; I'm no
engineer;and didn't even realize verifier.exe was there. If there is a
workaround;using verifier.exe; I'm going forward;not waiting for a
patent- this is is resolved/removed; from Connect;with no ability to even
see the results of bugs posted;because I am not in the private beta.
I hope this clarifies the situation. Two different Jeff's
Jeff
"Dan Mihai [MSFT]" wrote in message
...
Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was
installed
but that antivirus has never been installed. That sounds wrong so I hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some
Driver
Verifier information got added into the mix too. Why are these related
to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff
didn't
seem concerned about these other two AV products and there are no Driver
Verifier settings present on a system unless someone (Jeff) created
these
settings for some reason.

But it is very possible that I missed something - please clarify if that
is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it
can. Without it what happened is that you could run a scan with AVAST
(1/2 the equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the
AV entry and uncheck all the software drivers listed for "inspection"
by verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV program
of your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack
driver." The problem is though, which one since if you put driverquery
in the run box, you get a list of anywhere from 130 and up kernel stack
drivers (software and hdw). So how would you know which one was faulty?

Install the AV program you want to use: Avast will install but it will
tell you then on 5472 and up that it won't turn on the AV protection.
It will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error of
faulty driver you would disable deadlock detection per the first MSKB
below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps
you take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver Verifier
Is Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like
ya said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting with
5536 pre-RC1 and RC1 I found Avast needs a workaround to install which
is to uncheck driver inspection of Avast's software drivers typing
"verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and
it works perfectly. I understand you are comfortable with McAfee but
right now to enjoy the Beta try using Trend until the companies sort
things out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are
installed and
are not compatible. It requires me to remove them so it only exits
the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and it
hasn't
ever been installed. I search the machine for mcafee as well as the
registry
just to see if there was anything referencing the McAfee software
and there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless of
the
upgrade advisor's incorrect assessment of the software on the
machine?

This is the answer I received from folks at Microsoft who have been working
on the Avast! issue for build 5600:

"The Avast! folks are aware of these problems on build 5600. Please contact
them for the latest status. ".

Dan
--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Jeff" wrote in message
...
Dan;
No problem;
I've been trying to help all along;from 5384 thru 5600; and ;not to say
it's MINE;but; I've used my real name-Jeff-tp post in Ng's for a very long
time.
Is quite frustrating however;to be denied access to bug reports filed on
Connect;legitimate concerns;to try to help you guys; and getting a
patent-brush off; when I try to see the bug I posted; because I'm not in
the private Beta.
It would be great to have someone get back to me.
Jeff

"Dan Mihai [MSFT]" ,com wrote in message
...
Indeed, I didn't realize that there were two different Jeff's and they
were discussing about two separate problems in the same thread. :-)
Thanks for the clarification!

I hope this helps: I am aware of the Avast incompatibility with build
5600. I will try to find someone who has been working on that issue and
ask them to get back to you with the latest status. As far as I know it
is not related to Driver Verifier though, so I recommend not trying to
use verifier.exe in any way for this particular issue.

Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Jeff" wrote in message
...
Dan,
O.K.
#1 there are 2 Jeff's here. The 1st post is different;then my post.
I was responding to Chad about Avast; being fully able to
run-pre-5536 and now; being denied for incompatabilty in the rc1 tree.
Which Avast themselves;e-mailed me and stated it was an MSFT issue in
5536; that they were assured ; by MSFT themselves; that the issue would
be fixed in subsequent builds. Which;apparently; has not been addressed
in 5600.
Avast now runs scan only;but for all other features;ie shell
integration;web scan;e-mail protection etc. ; vista now reports blocking
due to driver incompatabilty. Further simple investigation of these
features being blocked;is that Avast is getting an RPC error.
And; to further the fact;as Chad has pointed out numerous times;
public feedback;through Connect;may be seen by you guys;but we have no
recourse to see the actions taken. Complicating the issue further; I'm
no engineer;and didn't even realize verifier.exe was there. If there is
a workaround;using verifier.exe; I'm going forward;not waiting for a
patent- this is is resolved/removed; from Connect;with no ability to
even see the results of bugs posted;because I am not in the private
beta.
I hope this clarifies the situation. Two different Jeff's
Jeff
"Dan Mihai [MSFT]" wrote in message
...
Sorry folks but I am confused by this discussion.

Jeff mentioned a problem where Setup thought that an antivirus was
installed
but that antivirus has never been installed. That sounds wrong so I
hope
Jeff can file this bug and the Vista Setup folks will figure it out.

Then I see some information about other two antivirus products. Some
Driver
Verifier information got added into the mix too. Why are these related
to
Jeff's Setup problem? They seem like apples and oranges to me. Jeff
didn't
seem concerned about these other two AV products and there are no
Driver
Verifier settings present on a system unless someone (Jeff) created
these
settings for some reason.

But it is very possible that I missed something - please clarify if
that is
the case.

Thanks,
Dan

--

This posting is provided "AS IS" with no warranties, and confers no
rights.


"Chad Harris" wrote in message
...
I am not 100% that it will get it in--my experience though is that it
can. Without it what happened is that you could run a scan with AVAST
(1/2 the equation) but you didn't have the AV up and guarding you.

What you do is to open up verifier per these directions, and go to the
AV entry and uncheck all the software drivers listed for "inspection"
by verifier. It will not impact the functionality of the AV.

But in this situation, if you haven't installed Avast or the AV
program of your choice, you have to.

My campaign here with MSFT, and I'm sending it to some of them is that
this will prevent some BSOD stop errors in Vista and XP I've seen that
have a "we've shut down the OS because of a corrupt kernel stack
driver." The problem is though, which one since if you put driverquery
in the run box, you get a list of anywhere from 130 and up kernel
stack drivers (software and hdw). So how would you know which one was
faulty?

Install the AV program you want to use: Avast will install but it
will tell you then on 5472 and up that it won't turn on the AV
protection. It will run a scan.

1) Type in run box: Verifier
2) If you were trying to stop BSODs that shut you down with an error
of faulty driver you would disable deadlock detection per the first
MSKB below.
3) Put button in create custom settings for developersNextSelect
Individual Settings from a full listMiscellaneous ChecksNextSelect
Driver's Name from a List
4) Uncheck the boxes by the AV program--in this case AVAST after you
install it.
5) Close.

See for ref:

I know you aren't using Norton here or tshooting a BSOD but the steps
you take are in he

Fatal System Error: 0x000000C4 If Deadlock Detection in Driver
Verifier Is Turned on and Norton Antivirus Is Installed

http://support.microsoft.com/kb/325672/en-us

How to Use DV to Troubleshoot Drivers
http://support.microsoft.com/kb/244617/en-us

CH


"Jeff" wrote in message
...
Chad,
Talk to me!!! How's that workaround go? I found verifier.exe like
ya said, now what next?
Jeff
"Chad Harris" wrote in message
...
I don't know Jeff. But you can use AVAST though 5472. Starting
with 5536 pre-RC1 and RC1 I found Avast needs a workaround to install
which is to uncheck driver inspection of Avast's software drivers
typing "verifier" in the run box (lose quotes).

In the last two builds including RC1 5600 I've been using Trend and
it works perfectly. I understand you are comfortable with McAfee
but right now to enjoy the Beta try using Trend until the companies
sort things out toward RTM.

CH


"Jeff K" wrote in message
...
On build 5384 upgrading to RC1, the upgrade compatibility check
incorrectly
reports that McAfee Internet Security and McAfee firewall are
installed and
are not compatible. It requires me to remove them so it only exits
the
upgrade when I okay the message.

McAfee is not installed (nor is any other antivirus software) and
it hasn't
ever been installed. I search the machine for mcafee as well as
the registry
just to see if there was anything referencing the McAfee software
and there
isn't a reference anywhere, but clearly the upgrade advisor see
something
that it flags as McAfee.

Is there a switch to force the upgrade to move forward regardless
of the
upgrade advisor's incorrect assessment of the software on the
machine?