logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

api-ms-win-core-libraryloader-l1-1-1.dll przy upgrade win7 do wim10

kacper69 5196 11
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
| New topic
  • #1 16910855
    kacper69
    Level 16  
    Posts: 255
    Help: 7
    Rate: 60
    I am trying to take advantage of the last free occasion (until the end of this year) WIN7 upgrade to WIN10.
    After running Windows10UpgradeAssisatnt, the application downloads from the network what it needs, checks my hardware - everything is OK, and with a specific attempt to update the following message appears:
    The program can not be started because the computer was not found api-ms-win-core-libraryloader-l1-1-1.dll Try reinstalling the program to fix the problem.

    I will add that I have an HP laptop, WIN7 32 bit, normal legal version, registered, everything OK.
    After a few unsuccessful attempts, I reinstalled the WIN7 system on this laptop, I downloaded all the updates that were possible and when trying to upgrade to WIN10 there is the same problem.
    What should I do to solve this problem?
    api-ms-win-core-libraryloader-l1-1-1.dll przy upgrade win7 do wim10win10 l...jpg (30.45 kB)You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #2 16910862
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    Perform a non-overlay installation W10.
  • ADVERTISEMENT
  • #3 16910868
    Pedros050
    Level 43  
    Posts: 17906
    Help: 2471
    Rate: 3901
    Hello. Give a laptop model because you do not all upgrade from win 7 to win 10, the more you have a 32 bit system, I have upgraded to 10 Home 32Bit but I downloaded the system from Microsoft and condition the original key in win 7.
  • ADVERTISEMENT
  • #5 16910884
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    kacper69 wrote:
    WIN7 32 bit

    @piterrr_ it is always puzzling why the OS 32 is originally in the laptop.
    There may be hardware limitations for the OS.

    Added after 1 [minutes]:

    @Kolobos it looks like the transfer (removal?) of wimgapi.dll fixes the problem ...
  • #6 16910897
    kacper69
    Level 16  
    Posts: 255
    Help: 7
    Rate: 60
    safbot1st wrote:
    Perform a non-overlay installation W10.


    I do not have WIN10 codes, so I want to do this upgrade from WIN7 to WIN10, because it does not need to have new WIN10 codes.
    The laptop model is: HP EliteBook 8440p with 4GRAM and I5 2.53 GHz.
  • ADVERTISEMENT
  • #7 16910899
    Pedros050
    Level 43  
    Posts: 17906
    Help: 2471
    Rate: 3901
    The key can be found in the registry.
    kacper69 wrote:
    you must have new codes for WIN10
  • #8 16910918
    kacper69
    Level 16  
    Posts: 255
    Help: 7
    Rate: 60
    PITERRR,
    From what you write, I understand that I can use my old WIN7 codes to install WIN10, which I have on a sticker or can I download them from registers by, for example, ProduKey?
    And are the same codes for WIN10 32bit and WIN10 64bit?
  • #9 16910936
    Pedros050
    Level 43  
    Posts: 17906
    Help: 2471
    Rate: 3901
    These are not the same but Microsoft will check the legality of this key with 7 32bit wines.
  • #10 16910975
    safbot1st
    Level 43  
    Posts: 21951
    Help: 2719
    Rate: 1583
    kacper69 wrote:
    And whether for the WIN10 32bit and WIN10 64bit versions

    You can see 64 bit drivers on your network, so you can "have fun" in 64-bit windows.
  • #11 16911612
    kacper69
    Level 16  
    Posts: 255
    Help: 7
    Rate: 60
    The method with the substitution of wimgapi.dll immediately solved my problem.
    WIN7 has been able to get to WIN10 without any problems.
    So the biggest thank you for the idea with this file replacement.
    I will stay on the 32 bit system, I do not need to change to a 64 bit system, everything I need works on this system OK.
    I will also add to those interested, I checked that after this upgrade, ProduKey detects the same activation code in WIN10, which was previously in WIN7.
  • #12 16911619
    Pedros050
    Level 43  
    Posts: 17906
    Help: 2471
    Rate: 3901
    kacper69 wrote:
    upgrade ProduKey detects the same activation code in WIN10, which was previously in WIN7
    Because it is assigned a key digitally to this laptop.
| New topic
Report a violation of the law

Topic summary

✨ The discussion revolves around a user experiencing issues while upgrading from Windows 7 to Windows 10 on an HP EliteBook 8440p laptop. The user encounters an error related to the missing api-ms-win-core-libraryloader-l1-1-1.dll file during the upgrade process. Various solutions are proposed, including performing a non-overlay installation of Windows 10, checking hardware compatibility, and using the original Windows 7 product key for activation. A successful resolution is achieved by replacing the wimgapi.dll file, allowing the upgrade to proceed without further issues. The user confirms that the activation code remains the same post-upgrade.
Generated by the language model.

FAQ

TL;DR: A 1-file swap fixed the Windows 7→10 upgrade error “api-ms-win-core-libraryloader-l1-1-1.dll.” “The method with the substitution of wimgapi.dll immediately solved my problem.” [Elektroda, kacper69, post #16911612]

Why it matters: This FAQ shows how to resolve the Upgrade Assistant error and activate Windows 10 without buying a new key, aimed at Windows 7 users hitting the DLL issue during in-place upgrades.

Quick Facts

How do I fix the “api-ms-win-core-libraryloader-l1-1-1.dll” error during the Windows 7 to 10 upgrade?

Close the Upgrade Assistant. Replace the wimgapi.dll it uses with a known-good copy, then relaunch the tool. Users reported the error vanished after this substitution. “The method with the substitution of wimgapi.dll immediately solved my problem.” [Elektroda, kacper69, post #16911612]

Is there a clean-install alternative if the in-place upgrade keeps failing?

Yes. Perform a non-overlay (clean) Windows 10 installation. This avoids Upgrade Assistant quirks and legacy software conflicts. Back up files first, then install Windows 10 from official media and activate with your qualifying license. [Elektroda, safbot1st, post #16910862]

Do I need to buy a new Windows 10 key when upgrading from Windows 7?

No. After upgrading, activation becomes a digital entitlement bound to your device. You won’t need to re-enter a new key on the same hardware. This was confirmed by users after the upgrade completed successfully. [Elektroda, Pedros050, post #16911619]

Can I reuse my Windows 7 product key for Windows 10 32‑bit or 64‑bit?

The keys are not identical across editions, but Microsoft validates a genuine Windows 7 key during Windows 10 setup. That allows activation when eligibility conditions are met. This worked for users moving within comparable editions. [Elektroda, Pedros050, post #16910936]

Where can I find my Windows 7 key before I start?

You can read it from the registry using tools like ProduKey, or from the OEM sticker on your laptop. Retrieve it before you begin so you can validate eligibility or compare after upgrade. [Elektroda, Pedros050, post #16910899]

What exactly triggers this DLL error in the Upgrade Assistant?

The Upgrade Assistant launches, downloads files, and checks hardware. Then it fails to start properly due to the DLL dependency issue shown in the message. Substituting wimgapi.dll resolved the launch failure for affected users. [Elektroda, kacper69, post #16910855]

Quick 3‑step: How do I substitute wimgapi.dll safely?

  1. Close Windows10UpgradeAssistant.
  2. Back up the wimgapi.dll used by the tool, then replace it with a known‑good copy.
  3. Run the Upgrade Assistant again and continue the upgrade. This cleared the error for the thread’s author. [Elektroda, kacper69, post #16911612]

Will Windows 10 64‑bit work on my HP EliteBook 8440p?

A contributor confirmed 64‑bit drivers are available, so running 64‑bit Windows is feasible on that model. Verify drivers for storage, chipset, graphics, and Wi‑Fi before switching architectures. “You can have fun in 64‑bit windows.” [Elektroda, safbot1st, post #16910975]

Is staying on 32‑bit Windows 10 acceptable for everyday use?

Yes, if your apps and peripherals work and memory needs are modest. The original poster stayed on 32‑bit and reported everything needed worked fine after the upgrade. This is a pragmatic choice on older laptops. [Elektroda, kacper69, post #16911612]

Does the Upgrade Assistant check hardware before failing?

Yes. In the reported case, the assistant downloaded components and passed hardware checks. The failure occurred at the start of the actual upgrade phase with the DLL error. [Elektroda, kacper69, post #16910855]

After upgrading, will ProduKey show the same key as Windows 7?

In this case, yes. ProduKey displayed the same activation code in Windows 10 as before in Windows 7. This helped verify successful activation post-upgrade. [Elektroda, kacper69, post #16911612]

Could a laptop’s original 32‑bit OS indicate limitations for Windows 10?

It can. Some laptops shipped with 32‑bit systems, reflecting hardware or vendor limits at the time. Assess CPU support and driver availability before moving to 64‑bit. An expert noted possible hardware limitations in such cases. [Elektroda, safbot1st, post #16910884]

What specific hardware was upgraded successfully in the thread example?

An HP EliteBook 8440p with an Intel i5 2.53 GHz CPU and 4 GB RAM upgraded from Windows 7 32‑bit to Windows 10 after the DLL fix. This provides a useful reference profile. [Elektroda, kacper69, post #16910897]
Generated by the language model.
ADVERTISEMENT