playwright: [BUG] Launching Chromium on Windows complains about missing libraries

Context:

• Playwright Version: 1.3.0
• Operating System: Windows 7
• Node.js version: 12.18
• Browser:Chromium

Code Snippet

const { chromium } = require('playwright');

(async () => {
  const browser = await chromium.launch();
  const context = await browser.newContext();
  const page = await context.newPage();


  await browser.close();
})();

Describe the bug Chromium doesn’t work, but other browsers seems to work fine

Console Output:

G:\GitHub\quran-api>set "DEBUG=pw:api" && node dircheck.js
(node:16052) UnhandledPromiseRejectionWarning: Error: browserType.launch: Host s
ystem is missing dependencies!

Full list of missing libraries:
    api-ms-win-core-winrt-error-l1-1-0.dll

Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs
.
    at validateDependenciesWindows (G:\GitHub\quran-api\node_modules\playwright\
lib\server\validateDependencies.js:78:11)
    at async validateDependencies (G:\GitHub\quran-api\node_modules\playwright\l
ib\server\validateDependencies.js:47:16)
    at async Object.validateHostRequirements (G:\GitHub\quran-api\node_modules\p
laywright\lib\server\validateDependencies.js:34:5)
    at async Chromium._launchServer (G:\GitHub\quran-api\node_modules\playwright
\lib\server\browserType.js:154:13)
    at async Chromium._innerLaunch (G:\GitHub\quran-api\node_modules\playwright\
lib\server\browserType.js:76:61)
    at async ProgressController.run (G:\GitHub\quran-api\node_modules\playwright
\lib\progress.js:75:28)
    at async Chromium.launch (G:\GitHub\quran-api\node_modules\playwright\lib\se
rver\browserType.js:62:25)
    at async G:\GitHub\quran-api\dircheck.js:4:19
(node:16052) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
 error originated either by throwing inside of an async function without a catch
 block, or by rejecting a promise which was not handled with .catch(). To termin
ate the node process on unhandled promise rejection, use the CLI flag `--unhandl
ed-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejecti
ons_mode). (rejection id: 1)
(node:16052) [DEP0018] DeprecationWarning: Unhandled promise rejections are depr
ecated. In the future, promise rejections that are not handled will terminate th
e Node.js process with a non-zero exit code.