[7" Kindle Fire HD General] SilentlyScreaming:
Sorry for the delay; my birthday, a new PC (seven years since last one!), kids, and a few alcohol-fuzzied evenings mean I've not been on top of things here.

OK, so a few notes as I go through your original post (welcome btw!)

(this part also worth a read by proxenusa, as a possible indicator of some extra clarification needed in the OP)

Removing the ghost items within Window's device manager only really applies to anything that is Amazon/ADB/Android related. The items you attempted to remove from non-P'n'P were probably not related to your kindle, but by the sounds of it (not actually removed), your PC wasn't fubarred by these removals, so you had some good luck anyway!

Re receiving several success messages - this is an issue I've brought up previously. In some cases, the message is misleading, as the only real success achieved can be that the batch file hasn't crashed out entirely. This does not mean that the individual action within the step you picked actually succeeded. I need to backup and start from a fake "virgin" kindle sometime to create proper bug tracking type thingies.

Re drivers not being updated by Windows when you point it to the directory with the INF etc files in. Don't try this unless you're willing to take more big risks, but I've forced Windows to accept a driver it didn't think matched the hardware before, especially with Samsung Galaxy Ace2 phones. Let me know if you're will to go that route, though you should be comfortable undoing the mess this can cause.

Re being verbose, don't apologize to anyone (in this thread at least!) for that. The more details you provide, the more likely it is that someone will randomly catch on to something "not quite right" and find a solution for you, possibly even for other members who have had issues, but not always provided the background info we need to try and assist each other.

Re your confusion over a step 12 reference, no, the Kindle doesn't need to be (shouldn't?) connected at this point, as installing drivers is only (at that moment in time) relevant to your Windows PC. For example, you can often install drivers for a webcam, a scanner, a gamepad etc. etc. in advance, before you even purchase the new hardware. The fact that you're installing these drivers from within KFFA does not mean that the Kindle needs to be involved at all, at that point.

Re the path statement,

simplified examples of valid PATH environment thingamabobs would be

C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Calibre2\;;C:\Program Files\Lucidlogix Technologies\VIRTU MVP

the first entry will have just the path at the beginning, BETWEEN the first and second entry, there should be a semi-colon ( ; ), then another path. Whether the previous or subsequent path listed happens to end in a backslash ( \ ) should not in anyway effect the c:\windows\system32 or ( %SystemRoot%\system32 ) path. Nor should it effect that particular path entry either, AFAIK.

PS I'm in no way affiliated with proxenusa, KFFA, or pretty much anything here. I'm just a fellow Kindle/Android user with a history in tech support, and a bad (for me and my wallet, though sometimes useful for assisting others) ideology of "if it ain't broke, you've not tweaked enough yet". TGA member who had that as his sig, feel free to remind me who you are, and I'll gladly properly attribute here ;)

PPS I fully realize that what I've just typed is not likely to directly lead to you sorting your problem. I've posted in an attempt to help you better understand what you've done and the instructions themselves, and also with a vague hope that another member here will read some of this, pay some attention and have a brainstorm that leads to a eureka moment of "of course, Marthal needs to do XYZ before ABC has a chance of working".

---------- Post added at 09:37 PM ---------- Previous post was at 09:26 PM ----------

When it comes to native Amazon android apps, I'd actually err on the side of caution (despite my overall device/hardware quote above), and if something works as wanted, NEVER allow an update. I don't trust Amazon to not try and force through OS updates (despite disabling OTA) via any sort of backdoor method involving updating other routines. I don't blame them (hardware sold at practically a loss, at least during some sales), as they need to earn money through in-house book/app/media purchases, but I do desire to keep my guard up. If an Amazon core app gets an update that has a feature I'd kill for, I'd first perform a few total backups, THEN allow an update (without enabling AUTOupdate). If the Kindle survives in it's rooted, OS-not updated, personal choice of launcher respected- mode, I'll breath easy. If not, restore, and trust them a little less ;)