Sys file dumped on desktop after bios flash
On a Dell 8930 W1064Pro I got a message to flash the bios. URGENT. I downloaded the package and flashed. This left two icons on my computer: "Removed apps.html" and, more problematic, the system file "amifldrv64.sys." Three months ago I also flashed the biosand just the amifldrv64.sys appeared on the desktop. Without too much forethought, I renamed it (I know don't mess with system files), and rebooted and the system went into BSOD loop of restarting. Tried everything to stop it. Went to DOS to try to find the file and rename it and it was gone. I called the local tech I use. They said the only way to recover the machine was to reinstall the OpSys, which, of course, wiped my programs and data. Data was triple backed up, no problem. And whatever the tech did then, he left a "Removed apps.html" list on my desktop.
Now, as I first said, after the "urgent" flash, the same sys file appeared as well as a html list of apps removed (none had been actually removed). It's easy enough to just delete the html file. (I wish I knew why that file, created in a reinstall was back.) Real problem is the amifldrv64.sys. Sure, I can set don't show hidden files then add the h attribute to the file and its icon disappears. That's fine of an .ini, but I think leaving a sys file on the desktop is begging for trouble.
On the Dell forum site https://www.dell.com/community/Inspiron-Desktops/Inspiron-3650-BIOS-update-amifldrv64-sys/td-p/6090239 there are suggestions that, conflated, come down to this: make copies of the amifldrv64.sys that is on the desktop, put one copy in system.32 and another in sysWOW64, then go back to desktop and rename to something like amifldrv64.new, reboot, if all's well move the renamed file to a storage folder.
BUT THERE IS NO REPORT FROM THE USER WHO WAS ADVISED TO TRY THE ABOVE. Instead, he asked the same question again. Thus I bring the problem and a solution proposed by a user here, hoping one of you has had the same problem.
Now, as I first said, after the "urgent" flash, the same sys file appeared as well as a html list of apps removed (none had been actually removed). It's easy enough to just delete the html file. (I wish I knew why that file, created in a reinstall was back.) Real problem is the amifldrv64.sys. Sure, I can set don't show hidden files then add the h attribute to the file and its icon disappears. That's fine of an .ini, but I think leaving a sys file on the desktop is begging for trouble.
On the Dell forum site https://www.dell.com/community/Inspiron-Desktops/Inspiron-3650-BIOS-update-amifldrv64-sys/td-p/6090239 there are suggestions that, conflated, come down to this: make copies of the amifldrv64.sys that is on the desktop, put one copy in system.32 and another in sysWOW64, then go back to desktop and rename to something like amifldrv64.new, reboot, if all's well move the renamed file to a storage folder.
BUT THERE IS NO REPORT FROM THE USER WHO WAS ADVISED TO TRY THE ABOVE. Instead, he asked the same question again. Thus I bring the problem and a solution proposed by a user here, hoping one of you has had the same problem.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
John,
I didn't download the flash program through Win10. I went to the Dell divers website to check if, in fact, it was urgent. I wish I'd known about exploding the bios in another file. I could have made one called bios. Back to the issue.
AndyAdler: I did that about three months ago after a flash - deleted the sys file left behind - and I got Blue-screen loop disease. Tech had to reinstall system. Not going there again. As John indicated, different machines tweak their bios programs to put the file where they want. And somewhere in the system (not in reg) there is an instruction that this particular sys file needs to stay where it's put. Other than hiding it or, as I've done, put it in a desktop folder tucked into a corner of the screen, I'm loath to try any solution that has not been tested.
I didn't download the flash program through Win10. I went to the Dell divers website to check if, in fact, it was urgent. I wish I'd known about exploding the bios in another file. I could have made one called bios. Back to the issue.
AndyAdler: I did that about three months ago after a flash - deleted the sys file left behind - and I got Blue-screen loop disease. Tech had to reinstall system. Not going there again. As John indicated, different machines tweak their bios programs to put the file where they want. And somewhere in the system (not in reg) there is an instruction that this particular sys file needs to stay where it's put. Other than hiding it or, as I've done, put it in a desktop folder tucked into a corner of the screen, I'm loath to try any solution that has not been tested.
On a Dell 8930 W1064Pro I got a message to flash the bios. URGENT.
This is in my opinion a BS message and personally I'd be thinking that it was a malware message. Who or what was the source of the message?
I downloaded the package and flashed. This left two icons on my computer: "Removed apps.html" and, more problematic, the system file "amifldrv64.sys." Three months ago I also flashed the biosand just the amifldrv64.sys appeared on the desktop.
So in 3 months you've updated your bios twice? One normally doesn't flash their bios except to add more functionality or fix a problem with the current bios . It is one of those 'If it's not broken don't fix it' items.
This is in my opinion a BS message and personally I'd be thinking that it was a malware message. Who or what was the source of the message?
I downloaded the package and flashed. This left two icons on my computer: "Removed apps.html" and, more problematic, the system file "amifldrv64.sys." Three months ago I also flashed the biosand just the amifldrv64.sys appeared on the desktop.
So in 3 months you've updated your bios twice? One normally doesn't flash their bios except to add more functionality or fix a problem with the current bios . It is one of those 'If it's not broken don't fix it' items.
It appears that is the way Dell has set up their updater. When you do it again, go methodically and see if you can tell the BIOS update where to explode to.
The installation instructions don't actually say don't run the update program from the desktop but they do say "browse to the location where you downloaded the file" which implies it shouldn't be run from the desktop.
ASKER
Alas I had downloaded it to the desktop and I do with most app installs. But your point is well taken, and John's suggestion to wait until the next bios update comes along and be more methodical in its install seems right to me. David: I checked at the dell drivers site, which marked the update urgent, and downloaded from there. The Dell software on the machine simply sends out notifications when it's software needs updating. I always download any driver from the manufacturers site. And, yes, I flashed the bios a few months back when I checked Dell's site and the bios update was labeled important. And your advice "...if it's not broken..." seems sound to me.
The november update only added more cpu support (they classify it as urgent.. I wouldn't unless I was wanting to use one of the newer cpu's)
The March Update is definitely important as it addresses several Intel CPU vulnerabilities
Q3 2018 Speculative Execution Side Channel Vulnerability and several more.
Dell and Lenovo released updated bios's on the same date (March 14th 2019)
The March Update is definitely important as it addresses several Intel CPU vulnerabilities
Q3 2018 Speculative Execution Side Channel Vulnerability and several more.
Dell and Lenovo released updated bios's on the same date (March 14th 2019)
Thanks. I was happy to help you resolve this
ASKER
Well, John, you were on the right highway. I bought my Dell through a corporate account which gave me access to high level tech support. I had called last week, got the typical clueless tech who noticed I could be bumped upstaird to their software team, a member of which just called me after a week of checking with his colleagues. That bios is designed to leave amifldrv64.sys in whatever folder it's launched from. So using a dell program on my machine (not my browser which is set to download everything to the desktop) he went to the Dell's driver site, downloaded the program to Downloads, launched it from there, where it left another amifldrv64.sys. Then we deleted the desktop original, rebooted twice to make sure all was well, and away we go. The simple instructions would be, move the bios update program to whatever directory you want (maybe a folder you could call bios) and launch it from there.
Thanks to everyone who contributed.
Thanks to everyone who contributed.
After installing the BIOS you should be able to delete the installation folder anyway. The AMI flash driver is used after the first reboot during the BIOS flash process but it's meant to be unlinked from the kernel after the next reboot.
ASKER
Another wrinkle. Thank you.
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
https://www.asrock.com/support/BIOSUI.asp?cat=Windows7