|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
Hi Loungers,
I’ve been receiving the attached message re above topic. Found an article on how to fix it, but hoped to get your blessing on its appropriateness before proceeding: https://support.microsoft.com/en-gb/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e
If it makes sense, I’ll give it a try. Always hesitant to proceed with techy stuff without Loungers’ stamp of approval! 🙂
Many thanks for your advice
Linda
I ran the scan via the Command Prompt. Is that all I need to do?
What was the report after running the scan ?
1. no problems found
2. found and fixed problems
3. found and couldn’t fix problems
Well, duh, that did make a huge difference! I’ve attached the new results, but I’m puzzled as it says all is well!
Linda
For issues like this I’d be inclined to do an over the top repair install, but always with an image backup at the ready.
Desktop Asus TUF X299 Mark 1, CPU: Intel Core i7-7820X Skylake-X 8-Core 3.6 GHz, RAM: 32GB, GPU: Nvidia GTX 1050 Ti 4GB. Display: Four 27" 1080p screens 2 over 2 quad.
This is Win7, not Win10/11
Appreciate the input and will provide a list of start up items as well as running the scan again without the spaces. I’ll be back to you once I have…likely in a day or two.
Again, my thanks for all your help!
Linda
Thanks, Satrow. Apologies for being away from this thread for so long…taxes called and I had to respond first! I’ll get at your link today and let you know how it goes.
Okay, Satrow. I’ve found my startup folder (duh, I should have remembered msconfig as I know I’ve used it before!). I’ve attached all the screenshots showing the checked programs and ALL the unchecked ones. Looks as if I’ve been in here before, killing start up programs. Can’t believe how many are in there in total. Yikes.
Does this help?
Thanks for understanding about the delay! 🙂
Linda
The link which satrow provided is good.
When you click on the Start-orb, do you have the Run option available? If not, ask how to.
If you do, click on it. In the box, key in msconfig, and click OK.
The panel which displays is not expandable; one of the 5 tabs is Startup.
There probably will be a long list, so rather than manually transcribing them out you may wish to create screen shots for posting.
To all helpful Loungers,
It’s fixed! Well, I’m pretty sure it is since I restarted and the error message did not appear.
I used “services.msc” to find Adobe Genuine Services, right clicked it and both “disabled” and “stopped” it.
Final Question/Thought:
I’m now debating if I should remove “Adobe Genuine Service” from the Programs list in Control Panel or just leave things as they are as in if it ain’t broke, don’t fix it” or “the message is gone, Linda: forget about it”.
Many thanks for your help and patience with all this…very much appreciated!
Linda
Well, phooey, Satrow and b. It just popped up again after I’d been away from the PC for a couple of hours. Another strange thing is that I couldn’t fine the program in Control Panel – Programs nor in Task Manager. I could find something similar only in “services.msc”, which is the one I tackled.
Any ideas on where to go next? It doesn’t seem to affect any operations of my computer so I suppose I could try to ignore it (bugs my Virgo self, however!).
Just re-checked Start Up folder, Services and found a lone Adobe program at the very bottom. I unchecked it. Maybe that will work?
Will post back in a couple of days once I’ve seen what happens with this latest attempt.
Many thanks and frustratingly yours,
Linda
@IreneLinda I don’t use the Adobe applications you have mentioned but I did try to use a Windows 7 VM to simulate the problem you are experiencing. I created a Windows desktop application and a dynamic link library (DLL) on which it depends. Then I deleted the DLL so that it could not be found when starting the application.
As you can see in the image below with items highlighted in red, the system issued the same error message and identified the executable in the error dialog caption. Now, DO NOT DISMISS the system error message. While it is still on the screen open Task Manager and click on the “Processes” tab. You should be able to find the executable identified in the system error message caption. Select the executable and right click to open a context menu and select “Properties”. The Property page that opens should enable you to find the specific executable that is causing the problem.
Api set api-ms-win-core-libraryloader-l1-2-1.dll was used for only one Windows API function. Even then, that implementation was subsequently changed by Microsoft to relocate that function to a different api set.
If you look at the full list on that Microsoft page, you’ll see 6 different API’s from api-ms-win-core-libraryloader-l1-2-0.dll that were moved to api-ms-win-core-libraryloader-l1-2-1.dll so there’s definitively more than just one API in it!
Also note, all the API’s displayed on that page are ones used by Windows 10 and @IreneLinda is using Windows 7!
Finally, regardless of whether any of the API’s might have been moved into a different version of libraryloader, the error message she’s getting indicates there’s an app installed on her PC that still needs api-ms-win-core-libraryloader-l1-2-1.dll to work.
@IreneLinda Be cautious and do not download this “missing” dll from non-Microsoft sources. Remember what Microsoft’s documentation said about API sets like api-ms-win-core-libraryloader-l1-2-1.dll —
The error is caused by Windows 7 attempting to run AdobeGCClient.exe when you start your system.
It seems to me that the simplest solution is to disable the mechanism that is causing the system to attempt to start this executable. Have you been able to locate this among the numerous items that are listed by running msconfig? You may need to expand the columns so that you can identify the problematic item by its file system location which you should now know if you fully followed the example that I posted earlier. @satrow pointed out several possible items for you to check in the image you posted for checked items.
In my opinion an application that has been correctly built to target Windows 7 would NEVER have a dependency on the api-ms-win-core-libraryloader-l1-2-1.dll api set that was first introduced in Windows 10. Consequently, my educated guess is that this Adobe executable should not have been installed on a Windows 7 system.
Bottom line — prevent it from starting and leave well enough alone afterwards.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
