ESRV_SVC_QUEENCREEK Cannot Be Found in Windows 11 and 10

If Event Viewer keeps telling you that ESRV_SVC_QUEENCREEK cannot be found, nothing on your computer is broken — something at startup is still trying to launch an Intel component that was uninstalled, and Windows is complaining about a program that is no longer there. The fix is to remove the leftover launcher, not to reinstall anything. Open Task Scheduler (press Windows key + R, type taskschd.msc, press Enter) and look for a task named USER_ESRV_SVC_QUEENCREEK; then check Task Manager → Startup apps, the registry Run keys and Services. Whichever one still points at C:\Program Files\Intel\SUR\QUEENCREEK\, confirm the file is genuinely missing and delete the entry. The message stops immediately.

The Saturday Jake spent chasing a program that did not exist

A customer brought a five-year-old laptop into Jake's shop with the complaint he hears twice a month: it feels slow on startup. Jake opened Event Viewer to see whether anything was screaming, and found the same entry repeating every single boot.

The description for Event ID 2 from source ESRV_SVC_QUEENCREEK cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted.

He lost most of a Saturday to it. System file checker. Disk check. He went looking for the service in services.msc, found nothing listed, and concluded the error was coming from somewhere he could not reach. He was one phone call away from quoting the customer a $60 reinstall.

"Read it again," Ethan said. "Out loud. All of it."

"Cannot be found. Either the component is not installed or the installation is corrupted."

"Stop there. It gave you the answer in the fourth word and you argued with it for six hours. The component is not installed. That is not a symptom, it is the diagnosis. Something is trying to start a program that somebody removed, probably years ago. Your job isn't to find the program. It's to find whatever is still asking for it."

Jake pushed back, reasonably. "Then why does every page I read send me to Services to disable it? I looked. It isn't in there."

"Because those pages were written for a machine where it still existed. On yours it has already been removed — which is exactly why the message says it cannot be found. You're reading the second half of the story with instructions for the first half."

Eleven minutes, once he knew that. One scheduled task, deleted. The laptop was still slow, because it had 4 GB of RAM and a spinning hard disk, which is a different conversation and a considerably more profitable one.

What ESRV_SVC_QUEENCREEK actually is

The name looks like a serial number and it is really four things stuck together. Take it apart once and you can see at a glance that it has nothing to do with anything you use.

The program behind it is esrv_svc.exe, and when installed it sits in:

SUR stands for System Usage Report — the data-collection half of the Intel Computing Improvement Program, an opt-in scheme where your machine sends Intel information about how its hardware is being used so Intel can spot driver problems and steer future designs. Telemetry, voluntary, and nothing on your PC depends on it.

Almost nobody installed it deliberately. It arrived bundled with the Intel Driver Update Utility, the small tool that used to scan your machine and offer Intel driver downloads. Millions of people ran that once, around 2015, to fix a graphics problem, then forgot it existed. Intel retired it: from 2017 the replacement is the Intel Driver & Support Assistant (Intel DSA), and the old utility has not been developed since.

Which sets up the whole problem. An unmaintained tool got removed — by a cleanup utility, a feature upgrade, a technician, the user — and the removal was not always complete. The folder went. The launcher stayed.

Why the message is worded so strangely

"The description for Event ID 2 from source X cannot be found" is not an Intel message at all. It is a generic Windows event log message, and it means something specific that almost nobody explains.

A program that writes to the event log first registers itself as a source and points Windows at a file holding the readable text for each of its error numbers. That registration lives under HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\, in a value called EventMessageFile. When the software is uninstalled the text file goes; the registration frequently does not.

So Event Viewer receives event number 2 from a source still on its books, goes looking for the words that explain it, finds nothing, and prints the only thing it can. What you are reading is two failures stacked: a missing program, and a missing explanation. That is why it reads like a riddle — so stop decoding the words and go find the launcher.

The pattern behind every cannot-be-found startup error

This is the part worth staying for, because it is not really about Intel.

Windows keeps a list of things to launch at startup — except it is not one list. It is at least five separate lists, in different places, edited by different tools, and none of them is ever checked against reality. Uninstallers are supposed to clean up their own entries. Uninstallers are written by people, in a hurry, years ago, and they routinely miss one.

The result is an orphan: an instruction to start a program, with no program at the other end. Windows follows it every boot, fails, writes a note in the log, and will keep doing that forever, because nothing in Windows goes back and audits the list.

"So this isn't an Intel bug," Jake said.

"It's barely a bug," Ethan said. "It's a filing error. Intel's just has the most memorable name, so it's the one everybody searches for. I've pulled the identical thing out of printer software, out of a trial antivirus somebody removed the lazy way, out of laptop-maker utilities wiped by a clean install. Same shape every time."

Here is that shape, and it is worth memorizing, because you will meet it again:

• 1. Find what is launching it. Five candidate places, below.
• 2. Read the full command line in the entry, not the friendly display name.
• 3. Prove the target file is missing. One command. Do not skip this.
• 4. Back the entry up — export the key or the task — so you can put it back.
• 5. Delete the entry, never the file. The file is already gone; that is the whole problem.

Learn it once and the next one costs five minutes instead of a Saturday. It also lets you ignore the hundreds of pages that answer these errors with "run sfc /scannow" — a tool that repairs damaged Windows files and has never had anything to do with a leftover third-party startup entry.

The five places a startup orphan can hide

Work down these in order. On this particular error, number four is usually the answer — which is why so many people check Task Manager, find nothing, and give up.

1. Task Manager, Startup apps

Press Ctrl + Shift + Esc. On Windows 11 the tab is in the left-hand rail and is called Startup apps; on Windows 10 it is along the top and is called Startup. Our post on the different ways to open Task Manager covers the other routes.

Right-click the column headings and switch on Command line — the most useful and least used option in the whole tool. Without it you are reading a publisher's chosen display name, and orphans are frequently named nothing like the file they launch. Anything pointing at the Intel SUR or QUEENCREEK folder is your entry. Right-click and choose Disable rather than deleting: instantly reversible, and it confirms you found the right one when the log goes quiet after a reboot.

Know the limit here: Task Manager shows two of the five places, not five. It reads the registry Run keys and the Startup folders. It does not show scheduled tasks and it does not show services. If your entry is not listed, that is information, not a dead end. Our guide to managing startup programs in Windows covers the routine housekeeping side of this tab.

2. The two Startup folders

Ordinary folders full of shortcuts, which Windows launches at sign-in. There is one for you and one for everybody on the machine, and people forget the second exists. Press Windows key + R and type each in turn:

If a shortcut in there points at a missing file, its icon usually turns into a blank white page — a genuinely useful visual tell. Right-click, Properties, read the Target box to be sure, then delete the shortcut. This is about as safe as this work gets: you are removing a pointer, and the original program, if it exists, is untouched.

3. The registry Run keys

Where most installers put their startup entries. Task Manager reads them but hides entries it does not recognize as apps, so it is worth looking directly. Open Registry Editor — Windows key + R, type regedit, press Enter. If that word makes you nervous, read our guide to opening Registry Editor safely, then take a registry backup. That second one is not a formality — thirty seconds, and it turns every mistake on this page into an inconvenience.

The last one is the trap. WOW6432Node is where 32-bit programs land on 64-bit Windows, and a great many of these old utilities were 32-bit. People check the first four, find nothing, and declare the registry clean.

To remove one, right-click the value on the right-hand side and choose Delete — but export the key first: right-click the key on the left, Export, save the .reg file. Double-clicking that file puts everything back.

4. Task Scheduler, where this one usually lives

Press Windows key + R, type taskschd.msc, press Enter, and click Task Scheduler Library in the left pane. That top-level folder is where third-party software drops its tasks; the Microsoft subfolder beneath it is Windows' own and should be left alone.

Look for USER_ESRV_SVC_QUEENCREEK. Select it and read the Actions tab in the pane below. What you will see alarms people:

That script calls task.bat, which calls task.exe. A script that runs a batch file that runs a program is not how anyone would build this today, and people have reported this task to Microsoft's forums assuming it was malware for exactly that reason. It isn't. It is clumsy packaging from a decade ago, and the Author field on the General tab reads Intel Energy Checker, which is your confirmation.

If the QUEENCREEK folder is gone, that chain can only fail. Right-click the task, choose Disable, reboot, confirm the log entry has stopped, then come back and Delete it — after right-clicking and choosing Export, which saves an .xml that restores the task exactly.

5. Services

Where the original version of this problem lived, and on older machines still where you will find it. Windows key + R, services.msc, Enter, and look for ESRV_SVC_QUEENCREEK or a display name mentioning Energy Server Service queencreek. If it is there, double-click it, set Startup type to Disabled, click Stop if available, Apply. Safe, reversible, the right first move. To see what it actually points at, open an administrator command prompt and run: 

Read the BINARY_PATH_NAME line. That is the file it will try to launch. If the file does not exist, the service definition is a pointer to nothing and can go:

Note the .exe. In PowerShell, sc on its own is an alias for Set-Content, so sc delete there does something completely different and confusing. Spelling out sc.exe works correctly in both Command Prompt and PowerShell. And if the service is present but simply refuses to start, that is a different problem entirely — our post on what to do when a Windows service will not start works through the error numbers.

Service errors like this rarely travel alone — if Event Viewer also shows

ESRV_SVC_QUEENCREEK cannot be found, that one is Intel's telemetry service, not a profile problem, and it has its own fix.

Prove it is orphaned before you delete anything

Jake pushed back again here, and he was right to. "I'm not deleting registry values on a customer's machine because a web page told me to. How do I actually know it's dead and not just something I don't recognize?"

"You test it," Ethan said. "One line. And if the answer comes back that it's still there, you stop and you delete nothing."

Take the path out of the entry you found — the part ending in .exe, .vbs or .bat — and put it in this, in quotes:

False means the file is not there. That is your proof, and it took a second. True means the software is still installed, the entry is doing its job, and your problem is a different one — go to clean removal instead.

Quote the path, because Program Files contains a space and without quotes the command reads it as two arguments. And check the whole chain where there is one: for the scheduled task, test task.vbs, and if that exists, test the task.exe it eventually calls, because a half-removed installation can leave the scripts and take the program.

Then back it up. Every removal here has a ten-second export: registry value — right-click the parent key, Export, save the .reg. Scheduled task — right-click, Export, save the .xml. Service — export HKLM\SYSTEM\CurrentControlSet\Services\ESRV_SVC_QUEENCREEK before sc.exe delete. Startup shortcut — move it to your desktop instead of deleting it.

And before any of that: disable, reboot, check the log. If the message is gone with the entry merely disabled, you found the right one. If it is still there, you have not — and you have deleted nothing you now have to explain.

If the Intel software is still installed, remove it properly

If Test-Path came back True, do not start deleting entries — you would be creating exactly the mess this page is about. Uninstall it the ordinary way and all five hiding places clear themselves.

Go to Settings → Apps → Installed apps on Windows 11, or Settings → Apps → Apps & features on Windows 10, and look for:

• Intel Computing Improvement Program — the telemetry program the SUR folder belongs to. Removing it is Intel's own advice for anyone getting errors mentioning sur, queencreek, sursvc or esrv.exe.
• Intel Driver Update Utility — the retired tool that installed it.
• Intel Energy Checker or Intel System Usage Report, listed separately on some older machines.

Our walkthrough on uninstalling a program properly in Windows covers the routes, including what to do when an entry refuses to uninstall. Reboot, then check Event Viewer again before deciding you have more to do.

What should you install in its place? Nothing is a perfectly good answer — Windows Update delivers most Intel drivers on its own, and on a laptop the manufacturer's support page ships versions tested against your exact model. If you do want the Intel tool, take the current Intel Driver & Support Assistant from Intel's detect page, not a copy of the retired utility from a download-aggregator site. Our post on how to update drivers in Windows covers the manual route, and slow boots after Intel updates is the companion piece.

Silencing Event Viewer for good

One optional extra for people who want the log genuinely clean. Even after the launcher is gone, the event source registration can survive, and anything raising an event under that name again produces the same unreadable message. In Registry Editor, look under:

A subkey named after the source in your message is the leftover registration. Export it, then delete it. Nothing about how your computer runs changes; it only stops Event Viewer keeping a bookmark for a source that no longer exists. Honest caveat: this is the most optional step on the page and the one with least to gain. If you are unsure, skip it — the startup entry was the thing causing the message, and this is tidying.

Can you just ignore it? Mostly yes

Most pages on this query will not tell you this, because a page that says "you can leave it" is a page you close. So, plainly: nothing on your computer depends on this component. It was optional telemetry. It does not touch your drivers, graphics, battery, network or Windows Update. The measurable cost of leaving it is one failed launch at boot and one line in a log you probably never open, and anyone quoting you a performance figure is guessing.

There is one real reason to clean it up, and it is not dramatic. Event Viewer is only useful when it is quiet. Its entire value is that when something breaks, the unusual entry stands out. A log with a guaranteed error every boot trains you to ignore errors, and the day one matters you will scroll straight past it. Our post on working with and clearing Event Viewer covers reading the logs once they are clean. Fix it because you want a diagnostic tool that works, not because your computer is at risk — it is not.

Is it malware? How to actually check

"A hidden service with a made-up name that runs a script that runs a batch file that runs a program," Jake said. "If you'd described that to me without saying Intel, I'd have wiped the machine."

"Fair," Ethan said. "And I'd rather you knew how to check than took my word for it, because ‘don't worry, it's fine’ is exactly what I'd be saying if I were wrong."

Almost never is the honest answer, and the message is mild evidence in its favor: it reports that a program is absent, and malware's whole objective is to be present. Check it properly anyway.

Check the location, then the signature

The legitimate file lives under C:\Program Files\Intel\SUR\QUEENCREEK\, and writing there requires administrator rights. Treat it as suspicious if a file with that name runs from anywhere under AppData, from a Temp folder, from Downloads or Documents, or from C:\Windows\System32\ directly — legitimate third-party software does not install itself there.

Then the check that settles it, which hardly anyone knows exists. Every legitimate Intel binary is digitally signed, and a signature cannot be forged without Intel's private key. Right-click the file, choose Properties, and look for a Digital Signatures tab — on Windows 11 you may need Show more options first. The signer should read Intel Corporation. No Digital Signatures tab at all is the red flag. Or in PowerShell:

A status of Valid with an Intel certificate is as close to certainty as you get. NotSigned or HashMismatch on a file claiming to be Intel's is a genuine problem.

When to stop reading and start scanning

One orphaned entry from an old uninstall is ordinary housekeeping. Escalate if two or more of these are also true:

• The entry comes straight back after deletion, and the file is back too.
• Windows Defender is off and will not turn on.
• Task Manager, Registry Editor or Task Scheduler close the instant you open them.
• Security and antivirus sites will not load while everything else does.
• Task Scheduler holds several unfamiliar tasks with random-looking names.

In that situation a normal scan from inside the running system is the weakest tool available, because anything capable of that is capable of hiding from a scanner that starts after it does. Use an offline scan, which reboots and scans before Windows loads — our post on running Windows Defender Offline covers it.

When it comes back, and other failure modes

You deleted it and it came back

Three realistic causes, and one question separates them: did the target file come back too? If it did, the parent software is still installed and rewrote its own entry — uninstall the program properly instead. If the file is still missing but the entry returned, you removed a copy rather than the source, most often by clearing the HKEY_CURRENT_USER Run value while an identical HKEY_LOCAL_MACHINE one remains, or by deleting a registry value that a still-enabled scheduled task recreates. Third possibility: some installers repair missing pieces the next time any part of the suite runs.

Access denied, or the service is greyed out

Almost always elevation. Registry Editor does not warn you that you lack rights — it simply refuses the write. Launch the tool as administrator: press Windows key + R, type the command, then press Ctrl + Shift + Enter instead of Enter. If it still fails, right-click the registry key, choose Permissions, and check that Administrators has Full Control. Take ownership only as a last resort, and only after exporting the key.

You cannot find it anywhere, but the message continues

Use Autoruns, the free Microsoft Sysinternals tool. It shows every startup location in Windows at once — far more than the five here — and has a filter to hide Microsoft entries so what remains is short. It is the correct tool for this job, it is genuinely free, and it comes from Microsoft with nothing bundled. Failing that, start Windows with all non-Microsoft startup items switched off; if the message disappears, re-enable things in halves until it returns. A few reboots, and it always finds the culprit.

It is a work laptop

Stop. On a machine managed by an employer, startup entries and scheduled tasks may be deployed and re-deployed by management software, so removing them locally either fails or is quietly undone overnight. Send your IT team the source name and the event ID. Two minutes for whoever owns the deployment; unwinnable for you.

Windows 11 and Windows 10: what sits in a different place

Every command, registry path and file path in this post is identical on both. Only the interface differs, and only slightly.

The Show more options row catches people. Several steps here — Properties on a file to reach Digital Signatures, Export on a registry key — live in a right-click menu that Windows 11 shortened. If an option you were told to look for is not there, click Show more options before concluding your machine is different.

One honest note, since this error is commonest on older hardware and many readers will be on Windows 10. Windows 10 reached end of support on 14 October 2025. It still boots and runs, and without Extended Security Updates it no longer receives security patches. Consumer ESU enrollment runs from Settings → Windows Update, and Microsoft extended the program in 2026 so enrolled machines stay covered into October 2027 — worth two minutes if you plan to keep the computer. The dates are in our post on when Windows 10 and 11 support ends. It has nothing to do with this error; it is simply the more consequential thing about that machine, and you deserve to be told.

Questions people actually ask about this

What is ESRV_SVC_QUEENCREEK?

It is the service name of the Intel Energy Checker component, whose program file is esrv_svc.exe and which normally lives in C:\Program Files\Intel\SUR\QUEENCREEK. SUR stands for System Usage Report, the data-collection part of the Intel Computing Improvement Program, and it reached most machines bundled with the old Intel Driver Update Utility. It is not a driver, it is not part of Windows, and nothing you use depends on it.

Why does it say ESRV_SVC_QUEENCREEK cannot be found?

Because it genuinely is not there. Something at startup is still trying to launch it, but the Intel software it belongs to was uninstalled or partly removed, so Windows complains about a program that no longer exists. The wording is Event Viewer telling you it cannot even load the text that would explain the error, because that text file was removed along with everything else.

How do I fix the ESRV_SVC_QUEENCREEK cannot be found error?

Find whatever is still launching it and remove that. Check Task Scheduler for a task named USER_ESRV_SVC_QUEENCREEK, then Task Manager Startup apps, then the registry Run keys, then Services. Confirm the file it points at is genuinely missing, then delete the entry rather than the file. If the Intel software is still installed, uninstall it from Settings and then Apps instead, because a clean uninstall clears all of them at once.

Is it safe to ignore the ESRV_SVC_QUEENCREEK error?

Largely yes, and we would rather say so than manufacture urgency. Nothing depends on this component, it was optional telemetry, and a startup entry that fails costs you milliseconds. The honest reason to clean it up is that a log full of predictable noise hides the one entry that matters on the day something real breaks. If you never open Event Viewer, you can leave it and lose nothing.

Is ESRV_SVC_QUEENCREEK a virus?

Almost never, and the message is mild evidence in its favor, because it reports that a program is absent rather than running. Check it properly all the same. The legitimate file is esrv_svc.exe under C:\Program Files\Intel\SUR\QUEENCREEK and it carries a valid Intel Corporation digital signature. Treat it as suspicious if a file with that name runs from AppData, Temp or Downloads, or if the signature is missing or fails to validate.

Where is the ESRV_SVC_QUEENCREEK startup entry hiding?

There are five places, and Task Manager shows you only two of them. Its Startup apps tab covers the registry Run keys and the Startup folders. It does not show scheduled tasks and it does not show services. On this error the entry is most often a scheduled task named USER_ESRV_SVC_QUEENCREEK, which is exactly why so many people look in Task Manager, find nothing, and assume the message is coming from somewhere invisible.

What is USER_ESRV_SVC_QUEENCREEK in Task Scheduler?

It is the per-user half of the same Intel component, and its author is listed as Intel Energy Checker. Its action runs Wscript.exe against a script called task.vbs in the Intel SUR QUEENCREEK folder, which calls task.bat, which calls task.exe. That chain looks alarming and is simply clumsy packaging. If the folder is gone the task can only fail, and deleting it is the correct repair.

Can I just delete the ESRV_SVC_QUEENCREEK service?

Yes, if it is genuinely orphaned. Run sc.exe qc ESRV_SVC_QUEENCREEK from an administrator command prompt, read the BINARY_PATH_NAME it reports, and check whether that file exists. If it does not, the service is a pointer to nothing and sc.exe delete ESRV_SVC_QUEENCREEK removes it cleanly. If the file does exist, uninstall the Intel software properly instead, because deleting the service leaves the rest of the program behind.

Does the Intel Driver Update Utility still exist?

Not as a current product. Intel replaced it from 2017 with the Intel Driver and Support Assistant, usually shortened to Intel DSA, which you get from the detect page on intel.com. The old utility has not been developed since, and it is the main reason these leftovers exist, because a great many machines had it installed years ago and then had it removed by something that did not tidy up after itself.

What is the Intel Computing Improvement Program and do I need it?

It is Intel's opt-in program that collects information about how your hardware is being used and sends it to Intel to help spot driver problems and shape future products. The System Usage Report folder, the ESRV service and the QUEENCREEK folder are its working parts. You do not need it. Your drivers, graphics and battery behave identically without it, and uninstalling it from the apps list is Intel's own advice when it starts producing errors.

How do I know a startup entry is genuinely orphaned before deleting it?

Read the full command line, take the file path out of it, and check whether that file exists. In PowerShell, Test-Path with the path in quotes answers it in one line and returns False if the file is missing. That False is your proof. Export the registry key or the scheduled task before you remove it, and never delete an entry whose target file is still present without first understanding what it does.

Why does the entry come back after I delete it?

Because something is recreating it, and there are only three realistic candidates. The parent software is still installed and rewrites its own entry when it runs. A second copy exists elsewhere, so you cleared the per-user one and the machine-wide one remains. Or a scheduled task recreates the registry value. Check whether the target file came back too: if the entry returned but the file is still missing, you removed a copy rather than the source.

Will removing this break my Intel drivers or graphics?

No. This is a reporting service, not a driver. Your graphics, chipset, wireless and management engine drivers are separate installations that do not reference it and keep working exactly as before. Nothing about display resolution, battery life, performance or Windows Update changes. The only thing you lose is the data being sent to Intel, which was optional in the first place and which the current Intel tooling can restart at any time.

Does this apply to other cannot be found startup errors?

Yes, and that is the useful part of this page. Any startup entry naming a program that is no longer installed produces the same class of message, whether it came from a printer suite, a trial antivirus, a laptop maker's utility or an old backup tool. The diagnosis never changes: find what is launching it, read the path, prove the file is missing, back up the entry, then delete the entry rather than the file.

Is this different on Windows 11 and Windows 10?

The mechanism, the registry paths, the commands and the scheduled task are identical. Only the interface differs. Windows 11 labels the Task Manager tab Startup apps and puts uninstalls under Settings then Apps then Installed apps, while Windows 10 uses a tab called Startup and a page called Apps and features. Windows 11 also hides older right-click options behind Show more options, which catches people out in Registry Editor and Task Scheduler.

What Jake's eleven minutes actually bought

The laptop had one scheduled task, authored by Intel Energy Checker, pointing at a folder that a Windows feature update had removed years earlier. Disable, reboot, log clean, delete, done.

"And that's it? After all that?"

"That's it," Ethan said. "The fix was never the hard part. Working out that the thing you were hunting for had already been removed — that was the whole job. You spent six hours looking for a program. There was no program."

Which is the sentence to carry away. When Windows says something cannot be found, believe it. That is not a hint that a file is damaged and needs repairing; it is a statement that a pointer has outlived its target. You are not looking for the missing thing — you are looking for whatever is still asking for it.

Once you can see that shape you own every one of these errors. The printer utility somebody removed in 2019. The antivirus trial that expired and got dragged to the bin. The laptop maker's update checker that a clean install left a shortcut for. Same message, same five hiding places, same five minutes.

Revision note. Originally published 28 February 2017, updated in November 2021, and rewritten on 9 August 2026. The original fix — stop the service in services.msc, set it to Disabled, or remove it with sc delete — was right for the machine it was written on, and it still works today on any computer where that service is actually listed. What changed is on Intel's side rather than ours: Intel retired the Driver Update Utility that installed this component and replaced it with the Driver & Support Assistant, so on the machines people bring us in 2026 the service has usually already been removed. That is exactly why so many readers now write in to say they followed the steps and could not find the service at all. So this rewrite keeps the service route where it belongs, adds the four other places a launcher can survive an uninstall — the scheduled task being by far the most common one now — and adds the proof test to run before you delete anything. We also added the general pattern, because once you can spot an orphaned startup entry you will not need a page like this again. If you found yours somewhere we have not listed, or your message names a source we have not covered, please write in through the contact page and tell us where it was hiding. Those messages are how this post became useful in the first place, and we read every one.