• Missing api-ms-win-core-libraryloader-11-2-1.dll

    Home » Forums » AskWoody support » Windows » Windows 7 » Questions: Windows 7 » Missing api-ms-win-core-libraryloader-11-2-1.dll

    Author
    Topic
    #2754479

    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

     

    Viewing 23 reply threads
    Author
    Replies
    • #2754494

      System file checker syntax:

      In an elevated Command Prompt (run as Administrator)
      sfc /scannow

    • #2754546

      Thanks, PK. I ran the scan via the Command Prompt. Is that all I need to do?

      Linda

      • #2755010

        Did you run the Command Prompt (cmd.exe) as Administrator?
        With NO space between / and scannow  (should look like this /scannow)

        • #2758891

          Sorry, I missed your message earlier! I did finally run it correctly, omitting the space.

           

           

    • #2754552

      @IreneLinda The missing file appears to be the name of what Windows calls an API set. This is a means of providing a level of indirection when applications load the dynamic link libraries that contain Windows API functions. In Windows 7 there were actually some physical DLLs that were used to implement this functionality. In modern versions of Windows API sets don’t exist as physical files. Rather, they are names that are recognized internally by the Windows loader and used to identify the actual DLLs that are to be loaded. There is a discussion of API sets here – Windows API sets

      On my Win10 22H2 system the API set “api-ms-win-core-libraryloader-l1-2-1.dll” resolves to “C:\Windows\System32\KERNELBASE.DLL”.

      What are you working with that tells you the API set is missing?

      • #2754586

        Good information and explanation, Eric. Thank you. I truly don’t know what exactly causes the error message…it occurs as I’m starting up. Everything seems to work fine regardless.

         

        Linda

         

        • #2754973

          So we understand what is happening please post a screenshot of the message when it occurs.

          Is this a new development?

          Did it start after you installed some application?

           

           

          • #2754998

            Thanks,Eric. It’s been going on for about 3 weeks. I haven’t added any software or apps. Weird thing…it was NOT there this morning. Maybe the scan worked?!

            Linda

             

            • #2755009

              Maybe the scan worked?

              No way for us to know.

              The image that you posted earlier appears to show that the sfc scan didn’t run. sfc seems to have only printed out the explanation of command line arguments.

              Its possible that there could have been other activity and output that didn’t show in the truncated image that was posted.

    • #2754559

      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

      SFC-scan

      • #2754589

        The weird thing, Alex, is that I can’t read the darn thing…it’s horizontally aligned and I can’t widen it to see what the text says, as yours does. I’ll attach what I’ve got to see if that helps.

        Linda

         

         

        • #2754622

          Linda, the command is     sfc /scannow    no space between / and scannow.

           

          Win 11 home - 24H2
          Attitude is a choice...Choose wisely

          • #2755588

            Well, duh, that did make a huge difference! I’ve attached the new results, but I’m puzzled as it says all is well!

            Scannow-Results

            Linda

             

    • #2754979

      List of Startup items please Linda, it looks like it might be *something* built for a later Windows version, or for a later library than you have installed that’s set to launch at Boot.

      MSConfig under the Startup tab.

    • #2754994

      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.

      1 user thanked author for this post.
      • #2754999

        This is Win7, not Win10/11

        1 user thanked author for this post.
    • #2755030

      Your screenshot shows the error is from AdobeGCclient.exe

      AdobeGCClient.exe System Error: What Is It & How to Fix It?

      • #2755586

        Thank, b. Will this work for Windows 7, too? I tried the first suggestion in the article but could not find the Adobe process in Processes in Task Manager.

        Also, the only Adobe on this computer is Adobe Reader. Will ending this process stop it from working when I need it to read Adobe pdfs?

        Linda

        P.S. Oops, I’m wrong. I have more Adobe items on this computer: Flash Pro CSS, Device Central CSS, Bridge CSS, ExtendScript Toolkit CSS, Extension Manager CSS. Do these relate at all to my error message?

         

    • #2755078

      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

      1 user thanked author for this post.
      • #2755587

        Satrow, I feel dumb but can’t figure out how to find the start up items to list for you. The methods I tried don’t seem to work or are too technical for my level of ability.

        Can you point me to an easy way to do this for Windows 7, please?

        Linda

         

        • #2755597

          No worries Linda, I had to do a quick search but came up with what feels like a very useful answer or two here: https://answers.microsoft.com/en-us/windows/forum/all/how-to-manageremove-startup-programs-in-windows-7/c2ff3fd1-3e32-46d9-9522-ec05034a2db1

          • #2758892

            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.

             

            1 user thanked author for this post.
          • #2758901

            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

             

            1 user thanked author for this post.
            • #2758928

              There are 2x possible Adobe products, one of which appears to match your error (Adobe GCClient, as pointed out by @b ) is the 2nd item down.

              You could uncheck it – but, as well illustrated by the many copies listed as unchecked to date, the best way to remove a startup is to start that software then find and unset the setting to autostart.

              I think a lesson on using Autoruns is needed soon to cleanup the unnecessary lines 🙂

            • #2759596

              Thanks for looking through ALL those start up programs. I’ll take your suggestion and find out what to do about Autoruns so I can clean up the list. I may first try unchecking the “guilty” program.

              One question first: do I need this program on my computer?

              I’ll hold off on doing anything until you have time to post back!

              With appreciation,

              Linda

               

        • #2755619

          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.
          Run

          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.

          1 user thanked author for this post.
          • #2758906

            Thanks, Paul, for your suggestion. I don’t have Run, but did find how to enter msconfig with no difficulty. As you can see from my reply to Satrow, I managed to take screenshots of the whole list.

            Linda

             

    • #2760511

      Hi All,

      First, my apologies for completely missing b’s post and his link to an article. Now, having read his article and one posted by Satrow, I think I’m ready to fix this issue. I’ll start with the simplest solution/s and work my way through the others, if necessary.

      Once I’ve got a solution, I’ll post back results and what worked.

      Many thanks and, again, sorry for missing some key posts earlier!

      Linda

    • #2760519

      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

      1 user thanked author for this post.
    • #2760692

      Good to see it appears to be fixed now, nice work Linda.

      I’ve no idea about “Adobe Genuine Service”, no experience of it; maybe some of the other Loungers have and can advise based on their experience/use of it?

    • #2760716

      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

       

      1 user thanked author for this post.
      • #2760866

        @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.

        StartError

         

        3 users thanked author for this post.
    • #2760898

      it looks like it might be *something* built for a later Windows version, or for a later library than you have installed that’s set to launch at Boot.

      I scanned my Window 7 Pro PC and two WIndows 10 Pro 22H2 PC’s (all 3 patched up thru March 2025) and can verify api-ms-win-core-libraryloader-|1-2-1.dll is not part of the standard Windows installation!

        On all three systems, the most current version was api-ms-win-core-libraryloader-l1-1-0.dll.

      @IreneLinda,

      That means it’s part of some 3rd party app you’ve installed and explains why the sfc scan didn’t find any problems (sfc checks for corrupt/missing Windows OS files, not 3rd party apps.)

      A web search for that file (please note, the filename ends in |1-2-1.dll not 11-2-1.dll) turned multiple solutions for fixing this error but they all require downloading a replacement file from sites that may not be trustworthy?!?!

      FYI, almost all those solutions indicated there are multiple different apps (programs, games, utilities, etc.) that may need this file so, if you can discovery exactly which of your apps is trying to use it, you could then either repair/reinstall it without needing to download a replacement that “might” be malicious.

      BTW, some of those results indicate that particular file is part of the Microsoft Visual C++ libraries and recommends downloading and installing the latest combined Visual C++ library (i.e. it contains all the “currently supported” versions.)

        Official Microsoft download link for x64 version.

        Official Microsoft download link for x86 version.

      Since you’re still using Windows 7, it’s possible it’d be part of an older no-longer-supported version.

      You should also consider that installing the combined Visual C++ library will install all supported versions, regardless of whether your current apps need them or not!

      • #2760919

        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.

        https://learn.microsoft.com/en-us/uwp/win32-and-com/win32-apis#apis-from-api-ms-win-core-libraryloader-l1-2-1dll

        FreeLibraryAndExitThread is a Windows API function and is unrelated to the functionality provided by the runtime support installed by Visual C++ redistributables.

         

        • #2761405

          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.

           

          1 user thanked author for this post.
          • #2761410

            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!

            The six you mention all were documented with “Introduced into api-ms-win-core-libraryloader-l1-2-0.dll in 10.0.10240. Moved into api-ms-win-core-libraryloader-l1-2-1.dll in 10.0.10586. Moved into api-ms-win-core-libraryloader-l1-2-0.dll in 10.0.14393.”

            So over the various Win10 builds mentioned they were in and out.

            Also note, all the API’s displayed on that page are ones used by Windows 10 and @IreneLinda is using Windows 7!

            Actually, if you looked up the individual Windows API functions mentioned you can see that they have been available since Windows 7 or below.

            In any event, the salient point is that api-ms-win-core-libraryloader-l1-2-1.dll is an api set, not a physical dll.  The loader in Windows 7 doesn’t know anything about it.

            The most likely underlying problem is that the application was created to run on Windows 10 and the reliance on api-ms-win-core-libraryloader-l1-2-1.dll would not be an issue since the Windows 10  loader would recognize the api set.  As I posted earlier, on my Win10 22H2 system that api set resolves to “C:\Windows\System32\KERNELBASE.DLL”

             

             

    • #2761280

      Wow, guys, terrific information. Thank you both so much for ALL the personal work you’ve done on my blasted nuisance issue.

      I had seen the C++ article, but am unwilling to tackle that particular fix…too technical for me.

      I’ll first try EricB’s solution and post back results. Give me a few days. I need a clear early morning head to tackle this stuff!

      Again, many many thanks.

      Linda

      • #2761354

        @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 —

        apisetdoc

         

        1 user thanked author for this post.
    • #2761421

      Eric, I found the process following your instructions. Now do I just end the process? The warning that came up (system might become unstable) made me nervous so thought I’d check back before proceeding.

      I await further instuctions.

      BYW: the error message comes up each time I use CTRL-ALT-DEL to access Task Manager. Is that something we need to pay attention to?

      Thanks again,

      Linda

       

       

       

      • #2761437

        I found the process following your instructions. Now do I just end the process?

        The intent of the instruction that I posted was for you to be able to identify the specifics of AdobeGCClient.exe so that you could prevent it from running when your system starts.

        All you need to do after you have found the specifics using Task Manager is to dismiss the system error message.  The AdobeGCClient.exe process should then terminate and disappear from Task Manager.

        BYW: the error message comes up each time I use CTRL-ALT-DEL to access Task Manager.

        This is a little confusing to me.  Are you saying that after you start your system and dismiss the error message the exact same error occurs if you use Ctrl+Alt+Del?  You had said earlier that the error only manifests at startup and otherwise everything seems to run fine.

    • #2761458

      I now understand, Eric. You’re right: closing the error message did remove the process from the list.

      This is a little confusing to me. Are you saying that after you start your system and dismiss the error message the exact same error occurs if you use Ctrl+Alt+Del? You had said earlier that the error only manifests at startup and otherwise everything seems to run fine.

      Sorry for the confusion. While the error message was open, each time I used Ctrl-Alt-Del, there was a ding which made me think the error was occurring.
      With the error message closed, this did not occur. Not sure why there was a ding, but looks as if it has nothing to do with our issue.

      Final question:

      What do I do from here? From what n0ads said, it seems there must be an app on my PC that needs the dll. I have no idea what it is and can’t think of any new app I’ve added that would cause the issue. Am I best to just ignore the error message or do we need to figure out the app that needs it or do I find and delete the dll?

      Sorry to be so confused myself!

      Linda

      • #2761487

        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.

        1 user thanked author for this post.
    • #2761731

      Thanks, Eric! I’ll spend some time reviewing your instructions and Satrow’s to try and locate the troublesome item. I will regard it as a challenge! I’ll post back results.

      BTW, I agree about your Windows 10/Windows 7 comment!

      Again, much appreciation for all the time you and the other contributors have spent working me through all this. Your assistance and your patience are beyond compare! THANK YOU!

      Linda

    • #2761787

      While searching for “AdobeGCClient.exe Missing api-ms-win-core-libraryloader-|1-2-1.dll” I ran across this Update for Universal C Runtime in Windows page containing the following tidbit that explains why a Windows 7 app would need a Windows 10 dll to work.

      Microsoft Visual Studio 2015 creates a dependency on the Universal CRT when applications are built by using the Windows 10 Software Development Kit (SDK). You can install this update on earlier Windows operating systems to enable these applications to run correctly.

      So the problem seems to be Adobe used the Windows 10 SDK when creating AdobeGCClient.exe, even for older versions of Windows, “assuming” all versions of Windows had been updated with a Visual C++ redistributable package that included the newer dll.

      I checked and, unfortunately, the file info for the downloads on that page indicate they only contain Api-ms-win-core-libraryloader-l1-1-0.dll not api-ms-win-core-libraryloader-|1-2-1.dll.

      I also checked all the Visual C++ redistributable packages on both my Windows 7 & Windows 10 PC’s and, even though they’re all up-to-date with the most current versions of Visual C++ redistributable available, none of them include the newer version either.

      That makes me wonder exactly which update would actually include it and where you’d get it.

      Maybe it’s in a specific Visual Studio/C++ SDK?

      1 user thanked author for this post.
      • #2761822

        Maybe it’s in a specific Visual Studio/C++ SDK?

        FWIW I installed the Windows 10 SDK (10.0.10586,212) since the 10586 build corresponds to the Microsoft api set documentation where api-ms-win-core-libraryloader-l1-2-1.dll is mentioned.

        As far as I could see it was not present in the numerous files that were installed by that Windows 10 SDK and was not included among the DLLs from that SDK that are allowed to be redistributed.

      • #2762048

        @EricB, I found a link at the Internet Archives that allowed me to download a copy of Microsoft’s “official” ISO for Windows 10 1511 build 10586 which is also “suppose” to include api-ms-win-core-libraryloader-l1-2-1.dll.

        I extracted the contents of the boot.wim file (i.e. all OS files it would install) and found, like you, it did not include that dll.

        The page you linked to states

        Linking WindowsApp.lib adds to your app dependencies on dlls that are present on all Windows devices.

        And api-ms-win-core-libraryloader-l1-2-1.dll did exist for Windows 10.0.10586.

        But, since neither Windows 1511 build 10586 nor the Windows 10 SDK 10586 contain it, exactly where the heck did it come from?!?!

        • #2762065

          But, since neither Windows 1511 build 10586 nor the Windows 10 SDK 10586 contain it, exactly where the heck did it come from?!?!


          @n0ads
          I believe that this api set is not an actual dll.  It does not exist as a file, but the api set is recognized and resolved as appropriate by the Windows 10 loader.

          I can’t prove it because I don’t have a working installation of the Windows 10 10586 build.  However, the fact the the loader on my Windows 10 22H2 system recognizes and resolves that api set in the absence of a physical file gives me high confidence that my explanation is correct.  After all, if a physical file was needed then calling the Windows API Function LoadLibrary for api-ms-win-core-libraryloader-l1-2-1.dll should fail.  But it succeeds and loads kernelbase.dll

           

    • #2762108

      Wow, I read through Eric and n0ad’s posts…so much detailed information! I could follow it, but can’t believe how you guys can delve into this material and come up with solutions!

      I’ll be back once I’ve done my homework as outlined in post #2761731.

      Yours in missing api’s

      Linda

      • #2762732

        I’ve been rereading everything in this thread to determine what I need to do. I think my plan should be as follows:

        1. Do not close the error message when it appears.
        2. Locate the specific executable using error message Properties as outlined in Eric’s post #2760866.
        3. Go back to the msconfig list and search for the file system location of the executable, expanding columns as needed.
        4. Locate it in the file system and disable it.

        Have I got it right? If you agree, I’ll follow these steps and report back results.

        My thanks again,

        Linda

         

         

        • #2762760

          Yep!

          4. Locate it in MSconfig and disable it there.

          cheers, Paul

        • #2762766

          Locate it in the file system and disable it.

          I take this to mean that you will locate the checked item(s) in msconfig with a matching file system location and then uncheck the item(s) in msconfig.

          The reason that my comment allows for more than one matching item is because its possible for a startup application to be specified in the registry per-machine in HKLM and also per-user in HKCU.

          2 users thanked author for this post.
    • #2763259

      Help. I didn’t quite manage to figure out what to do. I first searched for AdobeGenuineClient.exe (identified location via Properties) in Program Files to see if I could disable it there. It was nowhere to be found there.

      I next went to msconfig, but can’t find the exact executable. I’ve attached the jpg of the checked Start Up files. I see 2 Adobe files, but neither seems the correct one. Do I uncheck both of them? Either? Neither?

      Can anyone provide some more redirection. I’m not finding the items  I thought I could where I thought they’d be so obviously am doing something wrong!

      Thanks again,

      Linda

      • #2763285

        @IreneLinda First, the name of the executable according to the image of the error message that you first posted  is AdobeGCClient.exe, not AdobeGenuineClient.exe.

        If you followed the steps that I discussed in the example posted at https://www.askwoody.com/forums/topic/missing-api-ms-win-core-libraryloader-11-2-1-dll/#post-2760866 then you should see the property page for AdobeGCClient.exe which provides the file system location.  In the example image that I posted the file system location is highlighted in red.  The property page file system location on your system is where the problematic executable exists.  Hopefully that should be enough information for you to find matching items in msconfig after expanding columns.

        Finally, there are no images attached to your recent post.  If you post images of what you are looking at it will make things much easier for us if you continue to have difficulty getting this resolved  For example, I would like to see the images that show the system error message, task manager and the property page on your system when trying to track down AdobeGCClient.exe.

      • #2763315

        AdobeGCClient.exe is actually a Windows service (What is the Adobe Genuine Service?) so it won’t show up if you’re look for startup programs.

        Here’s how to stop it from automatically running.

          Press Win+R, enter services.msc, click OK

          Find Adobe Genuine Software Integrity Services, right-click it and select Properties

          If it’s “Running“, click the Stop button.

          Change the “Startup type:” to Disabled and click OK

        • #2763386

          @n0ads Windows services run in non-interactive session 0.  If AdobeGCClient.exe is a service executable the inability of the Windows 7 Service Control Manager (SCM) to start the executable due to a missing DLL would be reflected in the event log as a timeout error.  This is because the SCM did not receive a response to the service start command because the executable was not successfully started.

          Because session 0 is non-interactive there would not be any error message box displayed on the screen when the user signs-on.

           

           

    • #2763444

      Okay, Eric and n0ads, got it. I’ll try again in a day or two and let you know how it goes. Will also post the images you mention, Eric. Sorry I forgot to attach the last one. I’ll attach it by itself now and the others when I get back into this.

      Thanks so much for all your help!

      Linda

    • #2763961

      I’m back again. I read your instructional post again, did all  the steps leaving the error message open on my screen and found the .exe file in Processes in TaskManager.

      I’ve attached a few screenshots of some steps (missed Properties one as I’d closed it inadvertently, sorry!).

      I went back and re-read Satrow. Found the process in the list that seemed to match the Properties locaation (see highlighted one in attached), and unchecked it. I then opened Programs in Control Panel, found Adobe Genuine Service and uninstalled it.

      Once I’ve had a chance to restart (with crossed fingers!), I’ll post results.

      Hopefully,

      Linda

      1 user thanked author for this post.
      • #2763973

        Hopefully, the problem is resolved.  Unfortunately, none of the images posted in #2763961  give any visibility into the identification and location of AdobeGCClient.exe.

    • #2764322

      It’s gone! Today at mid-afternoon, the message has not popped up at all. I think it was the GCInvoker by Adobe highlighted in Start Up programs. Although it didn’t show in the image, its C drive location matched the Properties of the error message when checked via your earlier instructions. Unchecking that and then finding and uninstalling the program in Control Panel must have done the trick.

      Sorry it took me so long to interpret correctly the instructions and suggestions I was given. I sure appreciate the patience of tech-savvy Loungers with tech-not-at-all-savvy people such as I. Apologies, too, for posting unhelpful screenshots. I must have been too excited by the anticipation of having finally solved the issue!!

      I’ll post this, confirm one more time tomorrow that no message appears and then mark this thread as “solved”.

      Back to you with tomorrow’s findings…

      Linda

      3 users thanked author for this post.
      • #2765975

        Update: okay, Loungers all, I’ve given it several days and, joy of joys, the issue is fixed! 🙂

        It’s been quite a journey with a lot of learning (and a few missteps!) along the way. Thank you for sticking with me and helping me resolve it. As always, your knowledge and your patience in sharing it with me is appreciated enormously.

        I can now mark this as “resolved”.

        Thank you very much,

        Linda

         

        3 users thanked author for this post.
    • #2765976

      Guess I needed to click resolved first and then write. Here’s the note to add to the RESOLVED heading!

    Viewing 23 reply threads
    • The topic ‘Missing api-ms-win-core-libraryloader-11-2-1.dll’ is closed to new replies.