This content has been marked as final. Show 16 replies
I have the same issue. Adobe AIR 1.0.1 installed on Windows XP. Trying to install the Adobe Media Player. Ok to the 1st dialog (Publisher/System Acees), ok to the second dialog (shortcut/location) and immediately after, either BSOD on windrbnt.sys or reboot.
Starting app install of http://www.adobe.com/go/amp_install
UI SWF load is complete
Converting to C:\Documents and Settings\Admin\Local Settings\Temp\fla1D.tmp
Conversion is complete
AIR file is bound to version 1.0
app id com.adobe.amp
application is bound to this version of the runtime
Application is installed? false
Waiting for user confirmation
If you're seeing a system crash on install, it'd be helpful if you could capture a minidump for us to analyze. I believe they're in %systemroot%\minidump by default.
Oliver Goldman | Adobe AIR Engineering
I have minidump files. How do you want me to send one?
It's typically easiest if you can post one somewhere for download and send us the URL. You can try using share.acrobat.com for this if you need a place to post files.
Oliver Goldman | Adobe AIR Engineering
if the guy has windows XP and provided he has administrative rights, he can also go to the desktop, right click on "mycomputer" and select "manage"
Then select "event viewer" and "system". There he will have to look for the ones with a red cross.
I mean if the system rebooted it will say something here and he can know better what is going on.
I can post my minidump file on the web but I would like to send the URL by private message or email to somebody at Adobe. Is this possible?
I had AIR beta 2 installed previous to 1.0.1. I understand this might cause a conflict. I uninstalled beta 2 using the Add/Remove Windows panel before installing 1.0.1. Do you know an additional step that I could use to verify the complete removal of beta 2 before installing 1.0.1?
We've tracked down the blue screen on application install to an issue in a third-party application called "Folder Lock". Folder Lock installs the "windrvnt.sys" file that appears in the crashes, as lerognon noted. Applications other than Adobe AIR are also impacted by the Folder Lock issue.
Correct: desinstalling Folder Locker corrects the issue.
I'm getting the following error;
"An error occurred while installing Adobe AIR. Installation may not be allowed by your administrator. Please contact your administrator."
The log install output;
updater called with args:C:\Program Files\Common Files\Adobe AIR\Versions\1.0.6\Adobe AIR Updater.exe,-installupdatecheck
Windows XP Pro. SP2.
Let me know if you need anymore information.
@TeamTsuma: The log file you posted isn't from the install. It's from the 1.0 Beta 3 release. Is that still installed on your machine?
Beta 3 release has been on my machine before but has been removed. I've gone into the control panel and removed all Air apps and checked that I've not got any other version of Air on my machine.
I then tried the install and the log file outputted the same message
"updater called with args:C:\Program Files\Common Files\Adobe AIR\Versions\1.0.6\Adobe AIR Updater.exe,-installupdatecheck"
Is there a way of running a clean uninstall similar to the way it can be done for the Creative Suite because for some reason the installer thinks I've got the Beta on my machine.
I also tried the registry solution found
It worked for the earlier Beta but those keys are no longer there.
Thanks for looking into the problem.
You said you think the installer believes you have the Beta on your machine. What evidence do you have of that?
What's the name and timestamp on the log file you've pasted the contents of? The log file we need to debug this problem is called ".airinstall.log".
All sorted Cheers.
In my case, I get the blue screen of death. I've been searching through Google and found other people encountering the same problem, except they were using Windows Vista while I'm using Windows XP Professional.
I was able to install the AIR runtime with no problem, but I was trying to install HelloWorld.air from a book I got, and that's when the blue screen happened. I tried again, same thing. I wasn't about to let it happen a third time.
I set my system not to restart automatically when I get a blue screen so I could get the details, and it conflicted with WindrvNT.dll, something like that.