Bug Report Error with OBS studio 0.16.3

I downloaded latest version of OBS studio OBS studio 0.16.3. The installer updated my previous version to 0.16.3. And when I tried to run the program, an error occurred about " api-ms-win-core-version-l1-1-0.dll "

Who can help me with this problem ? I have windows 7 64bit

I already tried to find this dll at microsoft windows packets. Unsuccessfully =(
 

Beergnome

New Member
I am also getting the same error with both the 64 and 32 bit versions of Studio the error reads
obs64.exe - System Error
api-ms-win-core-version-l1-1-o.dll is missing from your computer. Try reinstalling the program to fix this problem.
 

Attachments

  • a8090e0f79d4827fa8a6008c492f560b.png
    a8090e0f79d4827fa8a6008c492f560b.png
    16.7 KB · Views: 101
  • a8090e0f79d4827fa8a6008c492f560b.png
    a8090e0f79d4827fa8a6008c492f560b.png
    16.7 KB · Views: 74

RytoEX

Forum Admin
Forum Moderator
Developer
@ReallyEvilSquirrel @Beergnome
Can you provide any available log files from when you try to launch OBS and this error occurs? Does OBS still launch after that error?

@Brian Rubin
Do you see the error message before OBS starts? Can you provide log files?

@SeriousSandal
I've been told by the plugin author that the AMD AMF encoder plugin should work on Windows 7, depending on your Service Pack and DirectX version. However, you need a compatible AMD graphics card for that, just like you need a compatible Nvidia graphics card to use NVENC, and you need a compatible Intel chipset or graphics card to use Quick Sync.
 

thghgv

Member
Getting this error when loading recently updated OBS studio "api-ms-win-core-version-l1-1-0.dll missing" under WIN7 x64. Windows resource protection found no corrupt/missing .DLL's. I suggest this be fixed ASAP. Rolling back to previous version until this gets resolved.
 

RytoEX

Forum Admin
Forum Moderator
Developer
Both the lead OBS developer and the author of the AMD AMF encoder plugin are aware of this issue. It is being fixed.
 

Xaymar

Active Member
I just told you that it's going to be in the next hotfix. For once, spend some time reading what I actually wrote.
 
Top