[2024-01-15 15:20:27.358] [info]  Omniverse Launcher 1.9.8 (production)
[2024-01-15 15:20:27.361] [info]  Argv: C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\NVIDIA Omniverse Launcher.exe
[2024-01-15 15:20:27.361] [info]  Crash dumps directory: C:\Users\Administrator\AppData\Roaming\omniverse-launcher\Crashpad
[2024-01-15 15:20:27.362] [info]  Start polling Launcher updates.
[2024-01-15 15:20:27.365] [info]  Can't access the C:\Users\Administrator\.nvidia-omniverse\config\omniverse.toml file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\omniverse.toml'
[2024-01-15 15:20:27.386] [info]  Can't access the C:\Users\Administrator\.nvidia-omniverse\config\omniverse.toml file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\omniverse.toml'
[2024-01-15 15:20:27.395] [info]  Can't access the C:\Users\Administrator\AppData\Roaming\omniverse-launcher\data\library.json file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\AppData\Roaming\omniverse-launcher\data\library.json'
[2024-01-15 15:20:27.399] [info]  Can't access the C:\Users\Administrator\AppData\Roaming\omniverse-launcher\data\installers.json file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\AppData\Roaming\omniverse-launcher\data\installers.json'
[2024-01-15 15:20:27.404] [info]  Running production web server.
[2024-01-15 15:20:27.414] [info]  HTTP endpoints listening at http://localhost:33480
[2024-01-15 15:20:27.414] [info]  HTTP endpoints listening at http://127.0.0.1:33480
[2024-01-15 15:20:27.417] [debug] Sharing: false
[2024-01-15 15:20:27.433] [info]  Started the Navigator web server on 127.0.0.1:34080.
[2024-01-15 15:20:27.437] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
(Use `NVIDIA Omniverse Launcher --trace-warnings ...` to show where the warning was created)
[2024-01-15 15:20:27.437] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[2024-01-15 15:20:27.815] [info]  Can't access the C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml'
[2024-01-15 15:20:27.815] [info]  Requesting the feature list for zh...
[2024-01-15 15:20:27.868] [info]  Registered omniverse-launcher for Windows.
[2024-01-15 15:20:27.874] [info]  Registered omniverse for Windows.
[2024-01-15 15:20:27.887] [info]  Initialized.
[2024-01-15 15:20:28.588] [info]  Enabled features for zh: { bugReports: false }
[2024-01-15 15:20:28.675] [info]  Logged in.
[2024-01-15 15:20:28.676] [info]  Can't access the C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml'
[2024-01-15 15:20:28.676] [info]  Can't access the C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml file:  ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\privacy.toml'
[2024-01-15 15:20:32.443] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:32.443] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
[2024-01-15 15:20:35.583] [info]  Requesting the feature list for en...
[2024-01-15 15:20:35.953] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 15:20:37.446] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:37.446] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
[2024-01-15 15:20:42.451] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:42.452] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[2024-01-15 15:20:47.462] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:47.462] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
[2024-01-15 15:20:52.465] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:52.466] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
[2024-01-15 15:20:57.094] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:20:57.472] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:20:57.473] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
[2024-01-15 15:21:02.473] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:02.473] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
[2024-01-15 15:21:07.479] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:07.479] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
[2024-01-15 15:21:08.120] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:21:08.121] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:21:12.482] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:12.483] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
[2024-01-15 15:21:15.818] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:21:15.819] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:21:17.484] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:17.484] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13)
[2024-01-15 15:21:22.499] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:22.499] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)
[2024-01-15 15:21:27.507] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:27.507] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
[2024-01-15 15:21:32.510] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:32.510] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)
[2024-01-15 15:21:37.511] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:37.511] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17)
[2024-01-15 15:21:41.834] [info]  WEB /favicon.ico
[2024-01-15 15:21:41.900] [info]  WEB /favicon.ico
[2024-01-15 15:21:42.524] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:42.524] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18)
[2024-01-15 15:21:47.534] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:47.534] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 19)
[2024-01-15 15:21:52.183] [info]  WEB /favicon.ico
[2024-01-15 15:21:52.544] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:52.544] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20)
[2024-01-15 15:21:57.558] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:21:57.559] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21)
[2024-01-15 15:22:02.571] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:02.571] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22)
[2024-01-15 15:22:02.823] [info]  Opening a second instance...
[2024-01-15 15:22:02.831] [info]  Running /install command...
[2024-01-15 15:22:07.579] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:07.580] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 23)
[2024-01-15 15:22:08.490] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:08.491] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 25)
[2024-01-15 15:22:11.718] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:11.718] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:12.582] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:12.582] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 27)
[2024-01-15 15:22:16.382] [info]  Opening a second instance...
[2024-01-15 15:22:16.389] [info]  Running /install command...
[2024-01-15 15:22:17.589] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:17.589] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 28)
[2024-01-15 15:22:22.031] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:22.031] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30)
[2024-01-15 15:22:22.595] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:22.595] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 31)
[2024-01-15 15:22:23.282] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:23.282] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:27.599] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:27.600] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 33)
[2024-01-15 15:22:28.857] [info]  Opening a second instance...
[2024-01-15 15:22:28.864] [info]  Running /install command...
[2024-01-15 15:22:32.601] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:32.601] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 34)
[2024-01-15 15:22:34.538] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:22:34.539] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36)
[2024-01-15 15:22:37.608] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:37.608] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 37)
[2024-01-15 15:22:42.622] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:42.623] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 38)
[2024-01-15 15:22:47.624] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:47.625] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 39)
[2024-01-15 15:22:52.628] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:52.628] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
[2024-01-15 15:22:55.337] [info]  WEB /login-result?state=eyJyZWRpcmVjdCI6Ii9leGNoYW5nZS9hcHAvYXVkaW8yZmFjZSJ9&ui_locales=en&code=YF-RVQJTNNsNsFgTUTOWeB9hfd2p4R_I53vgIhWJ8IELldwo0hBfBQwikuP9er72-b6pV5_xk9-Y3uKECQUskQ
[2024-01-15 15:22:55.457] [info]  WEB /favicon.ico
[2024-01-15 15:22:57.116] [info]  WEB /favicon.ico
[2024-01-15 15:22:57.633] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:22:57.633] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 41)
[2024-01-15 15:23:02.641] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:02.641] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42)
[2024-01-15 15:23:07.651] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:07.651] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 43)
[2024-01-15 15:23:12.660] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:12.660] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44)
[2024-01-15 15:23:15.029] [info]  WEB /favicon.ico
[2024-01-15 15:23:17.675] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:17.675] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 45)
[2024-01-15 15:23:22.688] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:22.688] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 46)
[2024-01-15 15:23:27.694] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:27.694] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 47)
[2024-01-15 15:23:32.708] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:32.708] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 48)
[2024-01-15 15:23:37.710] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:37.710] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 49)
[2024-01-15 15:23:42.717] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:42.717] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 50)
[2024-01-15 15:23:47.722] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:47.722] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 51)
[2024-01-15 15:23:52.733] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:52.733] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52)
[2024-01-15 15:23:55.972] [info]  WEB /favicon.ico
[2024-01-15 15:23:57.734] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:23:57.734] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 53)
[2024-01-15 15:24:00.551] [info]  WEB /favicon.ico
[2024-01-15 15:24:02.750] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:02.750] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 54)
[2024-01-15 15:24:02.994] [info]  Opening a second instance...
[2024-01-15 15:24:03.003] [info]  Running /install command...
[2024-01-15 15:24:07.766] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:07.766] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 55)
[2024-01-15 15:24:08.659] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:24:08.659] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 57)
[2024-01-15 15:24:12.781] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:12.782] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 58)
[2024-01-15 15:24:17.795] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:17.795] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 59)
[2024-01-15 15:24:22.810] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:22.810] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 60)
[2024-01-15 15:24:27.810] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:27.810] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 61)
[2024-01-15 15:24:32.813] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:32.813] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 62)
[2024-01-15 15:24:37.815] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:37.815] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 63)
[2024-01-15 15:24:42.826] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:42.826] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 64)
[2024-01-15 15:24:47.830] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:47.831] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 65)
[2024-01-15 15:24:52.838] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:52.838] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 66)
[2024-01-15 15:24:57.840] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:24:57.840] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 67)
[2024-01-15 15:25:02.841] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:02.841] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 68)
[2024-01-15 15:25:07.848] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:07.848] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 69)
[2024-01-15 15:25:12.852] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:12.852] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 70)
[2024-01-15 15:25:17.853] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:17.853] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 71)
[2024-01-15 15:25:22.854] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:22.855] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 72)
[2024-01-15 15:25:24.543] [info]  Opening a second instance...
[2024-01-15 15:25:24.552] [info]  Running /install command...
[2024-01-15 15:25:27.856] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:27.857] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 73)
[2024-01-15 15:25:30.203] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:25:30.204] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 75)
[2024-01-15 15:25:32.857] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:32.858] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 76)
[2024-01-15 15:25:37.873] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:37.873] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 77)
[2024-01-15 15:25:41.161] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:25:41.162] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:25:42.874] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:42.874] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 79)
[2024-01-15 15:25:47.888] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:47.888] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 80)
[2024-01-15 15:25:49.359] [info]  Opening a second instance...
[2024-01-15 15:25:49.366] [info]  Running /install command...
[2024-01-15 15:25:52.890] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:52.891] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 81)
[2024-01-15 15:25:55.006] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:25:55.006] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 83)
[2024-01-15 15:25:57.898] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:25:57.899] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 84)
[2024-01-15 15:26:02.907] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:02.907] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 85)
[2024-01-15 15:26:04.200] [info]  WEB /favicon.ico
[2024-01-15 15:26:06.452] [info]  WEB /favicon.ico
[2024-01-15 15:26:07.913] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:07.914] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 86)
[2024-01-15 15:26:08.068] [info]  Opening a second instance...
[2024-01-15 15:26:08.075] [info]  Running /install command...
[2024-01-15 15:26:12.922] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:12.922] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 87)
[2024-01-15 15:26:13.735] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:26:13.736] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 89)
[2024-01-15 15:26:17.925] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:17.925] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 90)
[2024-01-15 15:26:22.938] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:22.938] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 91)
[2024-01-15 15:26:23.134] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:26:27.940] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:27.940] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 92)
[2024-01-15 15:26:32.945] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:32.945] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 93)
[2024-01-15 15:26:37.945] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:37.945] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 94)
[2024-01-15 15:26:42.955] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:42.955] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 95)
[2024-01-15 15:26:43.658] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:26:43.659] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:26:47.962] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:47.962] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 97)
[2024-01-15 15:26:48.542] [info]  Opening a second instance...
[2024-01-15 15:26:48.549] [info]  Running /install command...
[2024-01-15 15:26:52.966] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:52.966] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 98)
[2024-01-15 15:26:54.205] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:26:54.206] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 100)
[2024-01-15 15:26:57.981] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:26:57.981] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 101)
[2024-01-15 15:26:59.036] [info]  Opening a second instance...
[2024-01-15 15:26:59.043] [info]  Running /install command...
[2024-01-15 15:27:02.983] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:02.984] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 102)
[2024-01-15 15:27:04.744] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:27:04.745] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 104)
[2024-01-15 15:27:07.984] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:07.984] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 105)
[2024-01-15 15:27:12.990] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:12.991] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 106)
[2024-01-15 15:27:17.999] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:18.000] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 107)
[2024-01-15 15:27:23.003] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:23.004] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 108)
[2024-01-15 15:27:28.012] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:28.013] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 109)
[2024-01-15 15:27:33.018] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:33.018] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 110)
[2024-01-15 15:27:38.025] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:38.025] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 111)
[2024-01-15 15:27:40.971] [info]  WEB /favicon.ico
[2024-01-15 15:27:43.032] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:43.033] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 112)
[2024-01-15 15:27:48.042] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:48.042] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 113)
[2024-01-15 15:27:53.057] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:53.057] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 114)
[2024-01-15 15:27:58.065] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:27:58.065] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 115)
[2024-01-15 15:28:03.075] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:03.075] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 116)
[2024-01-15 15:28:06.614] [info]  WEB /favicon.ico
[2024-01-15 15:28:06.720] [info]  WEB /favicon.ico
[2024-01-15 15:28:08.077] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:08.078] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 117)
[2024-01-15 15:28:13.080] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:13.081] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 118)
[2024-01-15 15:28:18.090] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:18.090] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 119)
[2024-01-15 15:28:19.551] [info]  WEB /favicon.ico
[2024-01-15 15:28:23.097] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:23.097] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 120)
[2024-01-15 15:28:24.812] [info]  Opening a second instance...
[2024-01-15 15:28:24.824] [info]  Running /install command...
[2024-01-15 15:28:28.104] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:28.104] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 121)
[2024-01-15 15:28:30.510] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:28:30.511] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 123)
[2024-01-15 15:28:32.946] [info]  Opening a second instance...
[2024-01-15 15:28:32.954] [info]  Running /install command...
[2024-01-15 15:28:33.104] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:33.104] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 124)
[2024-01-15 15:28:38.111] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:38.111] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 125)
[2024-01-15 15:28:38.612] [error] (node:24316) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:28:38.612] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 127)
[2024-01-15 15:28:43.113] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:43.114] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 128)
[2024-01-15 15:28:48.127] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:48.127] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 129)
[2024-01-15 15:28:53.142] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:53.143] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 130)
[2024-01-15 15:28:58.157] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:28:58.158] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 131)
[2024-01-15 15:29:03.161] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:03.161] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 132)
[2024-01-15 15:29:08.175] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:08.176] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 133)
[2024-01-15 15:29:13.187] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:13.188] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 134)
[2024-01-15 15:29:18.190] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:18.190] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 135)
[2024-01-15 15:29:23.205] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:23.206] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 136)
[2024-01-15 15:29:28.220] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:28.220] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 137)
[2024-01-15 15:29:33.222] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:33.222] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 138)
[2024-01-15 15:29:35.122] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:29:35.122] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:29:38.230] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:38.231] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 140)
[2024-01-15 15:29:42.216] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:29:42.216] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:29:43.242] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:43.242] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 142)
[2024-01-15 15:29:48.250] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:48.251] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 143)
[2024-01-15 15:29:53.252] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:53.252] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 144)
[2024-01-15 15:29:58.263] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:29:58.264] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 145)
[2024-01-15 15:30:03.275] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:30:03.276] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 146)
[2024-01-15 15:30:08.279] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:30:08.280] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 147)
[2024-01-15 15:30:13.289] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:30:13.289] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 148)
[2024-01-15 15:30:18.295] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:30:18.296] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 149)
[2024-01-15 15:30:23.299] [error] (node:24316) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
[2024-01-15 15:30:23.299] [error] (node:24316) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 150)
[2024-01-15 15:33:08.685] [info]  Omniverse Launcher 1.9.8 (production)
[2024-01-15 15:33:08.687] [info]  Argv: C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\NVIDIA Omniverse Launcher.exe
[2024-01-15 15:33:08.687] [info]  Crash dumps directory: C:\Users\Administrator\AppData\Roaming\omniverse-launcher\Crashpad
[2024-01-15 15:33:08.688] [info]  Start polling Launcher updates.
[2024-01-15 15:33:08.718] [debug] Reset current installer.
[2024-01-15 15:33:08.726] [info]  Running production web server.
[2024-01-15 15:33:08.735] [info]  HTTP endpoints listening at http://localhost:33480
[2024-01-15 15:33:08.736] [info]  HTTP endpoints listening at http://127.0.0.1:33480
[2024-01-15 15:33:08.739] [debug] Sharing: false
[2024-01-15 15:33:08.752] [info]  Started the Navigator web server on 127.0.0.1:34080.
[2024-01-15 15:33:08.755] [error] (node:28132) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, access 'C:\Users\Administrator\.nvidia-omniverse\config\auth.toml'
(Use `NVIDIA Omniverse Launcher --trace-warnings ...` to show where the warning was created)
[2024-01-15 15:33:08.755] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
[2024-01-15 15:33:09.105] [info]  Requesting the feature list for en...
[2024-01-15 15:33:09.193] [info]  Registered omniverse-launcher for Windows.
[2024-01-15 15:33:09.199] [info]  Registered omniverse for Windows.
[2024-01-15 15:33:09.210] [info]  Initialized.
[2024-01-15 15:33:09.868] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 15:33:10.030] [info]  Logged in.
[2024-01-15 15:33:18.671] [info]  Opening a second instance...
[2024-01-15 15:33:18.675] [info]  Running /navigate command...
[2024-01-15 15:33:18.676] [warn]  You are trying to use a blocker on a POP navigation to a location that was not created by @remix-run/router. This will fail silently in production. This can happen if you are navigating outside the router via `window.history.pushState`/`window.location.hash` instead of using router navigation APIs.  This can also happen if you are using createHashRouter and the user manually changes the URL.
[2024-01-15 15:33:55.542] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:33:55.543] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:34:10.682] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:34:10.682] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:34:17.903] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:34:17.903] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:34:32.067] [info]  WEB /nucleus
[2024-01-15 15:34:32.284] [info]  WEB /favicon.ico
[2024-01-15 15:34:36.060] [info]  Opening a second instance...
[2024-01-15 15:34:36.068] [info]  Running /navigate command...
[2024-01-15 15:34:36.069] [warn]  You are trying to use a blocker on a POP navigation to a location that was not created by @remix-run/router. This will fail silently in production. This can happen if you are navigating outside the router via `window.history.pushState`/`window.location.hash` instead of using router navigation APIs.  This can also happen if you are using createHashRouter and the user manually changes the URL.
[2024-01-15 15:36:15.545] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:36:15.546] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:36:22.340] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:36:22.340] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:37:30.290] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:37:30.291] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:38:56.091] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:38:56.092] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:25.233] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:25.234] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:34.841] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:34.841] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:58.981] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:39:58.982] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:40:06.159] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:40:06.160] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:40:27.174] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:40:27.175] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:40:28.324] [info]  WEB /favicon.ico
[2024-01-15 15:40:28.332] [info]  WEB /favicon.ico
[2024-01-15 15:40:28.343] [info]  WEB /favicon.ico
[2024-01-15 15:40:52.199] [info]  WEB /login-result?state=eyJyZWRpcmVjdCI6Ii9leGNoYW5nZSJ9&ui_locales=en&code=gb-A9LRVgDy34QIzpsX3XDigcRYKl9CnnGKcKQZmRwMy7_5fZWCft5TaDsCTTlkoiYzBoSmioSpC0ZTDViGRyA
[2024-01-15 15:40:52.317] [info]  WEB /favicon.ico
[2024-01-15 15:40:53.738] [info]  WEB /favicon.ico
[2024-01-15 15:40:55.994] [info]  WEB /favicon.ico
[2024-01-15 15:40:57.699] [info]  Opening a second instance...
[2024-01-15 15:40:57.707] [info]  Running /install command...
[2024-01-15 15:41:03.411] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:41:03.411] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
[2024-01-15 15:41:12.331] [info]  Opening a second instance...
[2024-01-15 15:41:12.339] [info]  Running /install command...
[2024-01-15 15:41:12.765] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:41:12.765] [error] Error occurred in handler for 'nucleus-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:41:18.074] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:41:18.075] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18)
[2024-01-15 15:41:18.321] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:41:18.677] [info]  Requesting the feature list for en...
[2024-01-15 15:41:19.026] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 15:41:21.313] [info]  Opening a second instance...
[2024-01-15 15:41:21.320] [info]  Running /install command...
[2024-01-15 15:41:21.743] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:41:26.961] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:41:26.961] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20)
[2024-01-15 15:41:29.537] [info]  Logged out.
[2024-01-15 15:41:57.984] [info]  Login URL opened.
[2024-01-15 15:41:58.087] [info]  Waiting for login result...
[2024-01-15 15:42:13.397] [info]  WEB /login-result?state=eyJlbGVjdHJvbiI6dHJ1ZSwicmVkaXJlY3QiOiIvbmV3cyJ9&ui_locales=en&code=vout1_SkBgmYHzg21TRxJIeZrfFKAq44fSrFrnuFRntBGcHT1669d_dvb15VQ3emauqNl7oOm5NTagV02QY4jw
[2024-01-15 15:42:13.513] [info]  WEB /favicon.ico
[2024-01-15 15:42:14.119] [info]  Opening a second instance...
[2024-01-15 15:42:14.127] [info]  Running /login command...
[2024-01-15 15:42:14.128] [info]  Received login result.
[2024-01-15 15:42:15.425] [info]  Logged in.
[2024-01-15 15:42:27.193] [info]  Requesting the feature list for en...
[2024-01-15 15:42:27.540] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 15:42:28.035] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:42:28.957] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:42:33.744] [info]  Opening a second instance...
[2024-01-15 15:42:33.751] [info]  Running /install command...
[2024-01-15 15:42:34.203] [warn]  Couldn't load featured components:  Error: Featured components are not available -- HTTP403.
[2024-01-15 15:42:39.360] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:42:39.360] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22)
[2024-01-15 15:42:47.795] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:42:47.796] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:17.113] [info]  Opening a second instance...
[2024-01-15 15:45:17.124] [info]  Running /install command...
[2024-01-15 15:45:22.822] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:22.822] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 25)
[2024-01-15 15:45:31.121] [info]  Opening a second instance...
[2024-01-15 15:45:31.128] [info]  Running /install command...
[2024-01-15 15:45:36.827] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:36.827] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 27)
[2024-01-15 15:45:49.725] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:49.725] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:51.505] [info]  Opening a second instance...
[2024-01-15 15:45:51.514] [info]  Running /install command...
[2024-01-15 15:45:54.049] [info]  Opening a second instance...
[2024-01-15 15:45:54.055] [info]  Running /install command...
[2024-01-15 15:45:54.378] [info]  Opening a second instance...
[2024-01-15 15:45:54.383] [info]  Running /install command...
[2024-01-15 15:45:54.566] [info]  Opening a second instance...
[2024-01-15 15:45:54.569] [info]  Running /install command...
[2024-01-15 15:45:54.746] [info]  Opening a second instance...
[2024-01-15 15:45:54.750] [info]  Running /install command...
[2024-01-15 15:45:54.883] [info]  Opening a second instance...
[2024-01-15 15:45:54.886] [info]  Running /install command...
[2024-01-15 15:45:55.041] [info]  Opening a second instance...
[2024-01-15 15:45:55.045] [info]  Running /install command...
[2024-01-15 15:45:55.201] [info]  Opening a second instance...
[2024-01-15 15:45:55.205] [info]  Running /install command...
[2024-01-15 15:45:55.369] [info]  Opening a second instance...
[2024-01-15 15:45:55.373] [info]  Running /install command...
[2024-01-15 15:45:55.551] [info]  Opening a second instance...
[2024-01-15 15:45:55.554] [info]  Running /install command...
[2024-01-15 15:45:55.685] [info]  Opening a second instance...
[2024-01-15 15:45:55.689] [info]  Running /install command...
[2024-01-15 15:45:55.852] [info]  Opening a second instance...
[2024-01-15 15:45:55.857] [info]  Running /install command...
[2024-01-15 15:45:56.015] [info]  Opening a second instance...
[2024-01-15 15:45:56.019] [info]  Running /install command...
[2024-01-15 15:45:56.180] [info]  Opening a second instance...
[2024-01-15 15:45:56.183] [info]  Running /install command...
[2024-01-15 15:45:56.356] [info]  Opening a second instance...
[2024-01-15 15:45:56.359] [info]  Running /install command...
[2024-01-15 15:45:56.535] [info]  Opening a second instance...
[2024-01-15 15:45:56.538] [info]  Running /install command...
[2024-01-15 15:45:56.690] [info]  Opening a second instance...
[2024-01-15 15:45:56.695] [info]  Running /install command...
[2024-01-15 15:45:56.853] [info]  Opening a second instance...
[2024-01-15 15:45:56.857] [info]  Running /install command...
[2024-01-15 15:45:57.016] [info]  Opening a second instance...
[2024-01-15 15:45:57.020] [info]  Running /install command...
[2024-01-15 15:45:57.213] [info]  Opening a second instance...
[2024-01-15 15:45:57.216] [info]  Running /install command...
[2024-01-15 15:45:57.226] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:57.226] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30)
[2024-01-15 15:45:57.374] [info]  Opening a second instance...
[2024-01-15 15:45:57.378] [info]  Running /install command...
[2024-01-15 15:45:57.538] [info]  Opening a second instance...
[2024-01-15 15:45:57.541] [info]  Running /install command...
[2024-01-15 15:45:57.713] [info]  Opening a second instance...
[2024-01-15 15:45:57.716] [info]  Running /install command...
[2024-01-15 15:45:57.876] [info]  Opening a second instance...
[2024-01-15 15:45:57.879] [info]  Running /install command...
[2024-01-15 15:45:58.048] [info]  Opening a second instance...
[2024-01-15 15:45:58.051] [info]  Running /install command...
[2024-01-15 15:45:58.218] [info]  Opening a second instance...
[2024-01-15 15:45:58.222] [info]  Running /install command...
[2024-01-15 15:45:58.404] [info]  Opening a second instance...
[2024-01-15 15:45:58.407] [info]  Running /install command...
[2024-01-15 15:45:58.578] [info]  Opening a second instance...
[2024-01-15 15:45:58.582] [info]  Running /install command...
[2024-01-15 15:45:58.718] [info]  Opening a second instance...
[2024-01-15 15:45:58.721] [info]  Running /install command...
[2024-01-15 15:45:58.894] [info]  Opening a second instance...
[2024-01-15 15:45:58.897] [info]  Running /install command...
[2024-01-15 15:45:59.050] [info]  Opening a second instance...
[2024-01-15 15:45:59.052] [info]  Running /install command...
[2024-01-15 15:45:59.219] [info]  Opening a second instance...
[2024-01-15 15:45:59.223] [info]  Running /install command...
[2024-01-15 15:45:59.411] [info]  Opening a second instance...
[2024-01-15 15:45:59.414] [info]  Running /install command...
[2024-01-15 15:45:59.568] [info]  Opening a second instance...
[2024-01-15 15:45:59.571] [info]  Running /install command...
[2024-01-15 15:45:59.739] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:45:59.739] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 32)
[2024-01-15 15:45:59.747] [info]  Opening a second instance...
[2024-01-15 15:45:59.751] [info]  Running /install command...
[2024-01-15 15:45:59.935] [info]  Opening a second instance...
[2024-01-15 15:45:59.939] [info]  Running /install command...
[2024-01-15 15:46:00.078] [info]  Opening a second instance...
[2024-01-15 15:46:00.081] [info]  Running /install command...
[2024-01-15 15:46:00.130] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.130] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 34)
[2024-01-15 15:46:00.254] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.254] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36)
[2024-01-15 15:46:00.264] [info]  Opening a second instance...
[2024-01-15 15:46:00.268] [info]  Running /install command...
[2024-01-15 15:46:00.402] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.403] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 38)
[2024-01-15 15:46:00.457] [info]  Opening a second instance...
[2024-01-15 15:46:00.460] [info]  Running /install command...
[2024-01-15 15:46:00.583] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.584] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40)
[2024-01-15 15:46:00.620] [info]  Opening a second instance...
[2024-01-15 15:46:00.624] [info]  Running /install command...
[2024-01-15 15:46:00.732] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.733] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42)
[2024-01-15 15:46:00.827] [info]  Opening a second instance...
[2024-01-15 15:46:00.831] [info]  Running /install command...
[2024-01-15 15:46:00.899] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:00.899] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44)
[2024-01-15 15:46:01.000] [info]  Opening a second instance...
[2024-01-15 15:46:01.003] [info]  Running /install command...
[2024-01-15 15:46:01.068] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.068] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 46)
[2024-01-15 15:46:01.161] [info]  Opening a second instance...
[2024-01-15 15:46:01.164] [info]  Running /install command...
[2024-01-15 15:46:01.221] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.221] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 48)
[2024-01-15 15:46:01.354] [info]  Opening a second instance...
[2024-01-15 15:46:01.357] [info]  Running /install command...
[2024-01-15 15:46:01.389] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.389] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 50)
[2024-01-15 15:46:01.540] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.541] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52)
[2024-01-15 15:46:01.545] [info]  Opening a second instance...
[2024-01-15 15:46:01.549] [info]  Running /install command...
[2024-01-15 15:46:01.693] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.693] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 54)
[2024-01-15 15:46:01.721] [info]  Opening a second instance...
[2024-01-15 15:46:01.724] [info]  Running /install command...
[2024-01-15 15:46:01.886] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:01.887] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 56)
[2024-01-15 15:46:01.898] [info]  Opening a second instance...
[2024-01-15 15:46:01.902] [info]  Running /install command...
[2024-01-15 15:46:02.019] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.020] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 58)
[2024-01-15 15:46:02.072] [info]  Opening a second instance...
[2024-01-15 15:46:02.076] [info]  Running /install command...
[2024-01-15 15:46:02.254] [info]  Opening a second instance...
[2024-01-15 15:46:02.258] [info]  Running /install command...
[2024-01-15 15:46:02.259] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.259] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 60)
[2024-01-15 15:46:02.389] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.389] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 62)
[2024-01-15 15:46:02.450] [info]  Opening a second instance...
[2024-01-15 15:46:02.454] [info]  Running /install command...
[2024-01-15 15:46:02.554] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.554] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 64)
[2024-01-15 15:46:02.623] [info]  Opening a second instance...
[2024-01-15 15:46:02.627] [info]  Running /install command...
[2024-01-15 15:46:02.741] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.741] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 66)
[2024-01-15 15:46:02.826] [info]  Opening a second instance...
[2024-01-15 15:46:02.830] [info]  Running /install command...
[2024-01-15 15:46:02.936] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:02.936] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 68)
[2024-01-15 15:46:03.030] [info]  Opening a second instance...
[2024-01-15 15:46:03.034] [info]  Running /install command...
[2024-01-15 15:46:03.062] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.062] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 70)
[2024-01-15 15:46:03.186] [info]  Opening a second instance...
[2024-01-15 15:46:03.189] [info]  Running /install command...
[2024-01-15 15:46:03.231] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.231] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 72)
[2024-01-15 15:46:03.392] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.392] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 74)
[2024-01-15 15:46:03.395] [info]  Opening a second instance...
[2024-01-15 15:46:03.399] [info]  Running /install command...
[2024-01-15 15:46:03.579] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.579] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 76)
[2024-01-15 15:46:03.593] [info]  Opening a second instance...
[2024-01-15 15:46:03.599] [info]  Running /install command...
[2024-01-15 15:46:03.738] [info]  Opening a second instance...
[2024-01-15 15:46:03.741] [info]  Running /install command...
[2024-01-15 15:46:03.742] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.742] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 78)
[2024-01-15 15:46:03.897] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:03.898] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 80)
[2024-01-15 15:46:03.950] [info]  Opening a second instance...
[2024-01-15 15:46:03.954] [info]  Running /install command...
[2024-01-15 15:46:04.123] [info]  Opening a second instance...
[2024-01-15 15:46:04.127] [info]  Running /install command...
[2024-01-15 15:46:04.129] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.129] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 82)
[2024-01-15 15:46:04.268] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.268] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 84)
[2024-01-15 15:46:04.330] [info]  Opening a second instance...
[2024-01-15 15:46:04.333] [info]  Running /install command...
[2024-01-15 15:46:04.393] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.393] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 86)
[2024-01-15 15:46:04.489] [info]  Opening a second instance...
[2024-01-15 15:46:04.492] [info]  Running /install command...
[2024-01-15 15:46:04.595] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.595] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 88)
[2024-01-15 15:46:04.685] [info]  Opening a second instance...
[2024-01-15 15:46:04.688] [info]  Running /install command...
[2024-01-15 15:46:04.737] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.737] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 90)
[2024-01-15 15:46:04.875] [info]  Opening a second instance...
[2024-01-15 15:46:04.879] [info]  Running /install command...
[2024-01-15 15:46:04.898] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:04.898] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 92)
[2024-01-15 15:46:05.049] [info]  Opening a second instance...
[2024-01-15 15:46:05.052] [info]  Running /install command...
[2024-01-15 15:46:05.110] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.110] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 94)
[2024-01-15 15:46:05.220] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.220] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 96)
[2024-01-15 15:46:05.244] [info]  Opening a second instance...
[2024-01-15 15:46:05.247] [info]  Running /install command...
[2024-01-15 15:46:05.412] [info]  Opening a second instance...
[2024-01-15 15:46:05.416] [info]  Running /install command...
[2024-01-15 15:46:05.452] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.452] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 98)
[2024-01-15 15:46:05.618] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.618] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 100)
[2024-01-15 15:46:05.727] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.727] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 102)
[2024-01-15 15:46:05.966] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:05.966] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 104)
[2024-01-15 15:46:06.170] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:06.171] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 106)
[2024-01-15 15:46:06.359] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:06.359] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 108)
[2024-01-15 15:46:06.519] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:06.519] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 110)
[2024-01-15 15:46:06.706] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:06.707] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 112)
[2024-01-15 15:46:06.836] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:06.837] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 114)
[2024-01-15 15:46:07.063] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.063] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 116)
[2024-01-15 15:46:07.268] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.268] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 118)
[2024-01-15 15:46:07.418] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.419] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 120)
[2024-01-15 15:46:07.597] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.597] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 122)
[2024-01-15 15:46:07.787] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.787] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 124)
[2024-01-15 15:46:07.958] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:07.959] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 126)
[2024-01-15 15:46:08.135] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:08.135] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 128)
[2024-01-15 15:46:08.360] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:08.360] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 130)
[2024-01-15 15:46:08.508] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:08.509] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 132)
[2024-01-15 15:46:08.752] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:08.752] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 134)
[2024-01-15 15:46:08.889] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:08.889] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 136)
[2024-01-15 15:46:09.110] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:09.110] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 138)
[2024-01-15 15:46:09.272] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:09.273] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 140)
[2024-01-15 15:46:09.416] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:09.416] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 142)
[2024-01-15 15:46:09.639] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:09.639] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 144)
[2024-01-15 15:46:09.827] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:09.827] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 146)
[2024-01-15 15:46:10.013] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.014] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 148)
[2024-01-15 15:46:10.165] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.165] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 150)
[2024-01-15 15:46:10.361] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.361] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 152)
[2024-01-15 15:46:10.549] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.549] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 154)
[2024-01-15 15:46:10.729] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.729] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 156)
[2024-01-15 15:46:10.923] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:10.923] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 158)
[2024-01-15 15:46:11.097] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:11.097] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 160)
[2024-01-15 15:46:14.744] [info]  Opening a second instance...
[2024-01-15 15:46:14.752] [info]  Running /install command...
[2024-01-15 15:46:20.412] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:20.413] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 162)
[2024-01-15 15:46:30.659] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:46:30.660] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:35.989] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:35.990] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:45.054] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:45.055] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:49.149] [info]  Opening a second instance...
[2024-01-15 15:54:49.156] [info]  Running /install command...
[2024-01-15 15:54:54.851] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:54:54.851] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 167)
[2024-01-15 15:55:40.572] [info]  Opening a second instance...
[2024-01-15 15:55:40.579] [info]  Running /install command...
[2024-01-15 15:55:46.216] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:55:46.216] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 169)
[2024-01-15 15:57:01.618] [info]  Opening a second instance...
[2024-01-15 15:57:01.625] [info]  Running /install command...
[2024-01-15 15:57:07.256] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:57:07.256] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 171)
[2024-01-15 15:58:50.655] [info]  Opening a second instance...
[2024-01-15 15:58:50.665] [info]  Running /install command...
[2024-01-15 15:58:56.365] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 15:58:56.366] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 173)
[2024-01-15 16:09:48.744] [info]  Opening a second instance...
[2024-01-15 16:09:48.755] [info]  Running /install command...
[2024-01-15 16:09:54.408] [error] (node:28132) UnhandledPromiseRejectionWarning: FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:09:54.408] [error] (node:28132) 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 terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 175)
[2024-01-15 16:21:56.396] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:21:56.396] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:22:11.010] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:22:11.010] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:27:00.920] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:27:00.921] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:39:10.142] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 16:39:10.143] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:31:08.293] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:31:08.293] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:46:56.978] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:46:56.979] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:54:49.678] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:54:49.679] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:54:56.689] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:54:56.690] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:55:25.105] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:55:25.106] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:55:39.349] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 17:55:39.350] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 20:15:37.639] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 20:15:37.640] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 20:23:53.584] [error] FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 20:23:53.585] [error] Error occurred in handler for 'prepare-install': FetchError: request to https://launcher-index-prod.s3.amazonaws.com/en/components.json failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\resources\app.asar\dist\main.js:8:56675)
    at ClientRequest.emit (node:events:513:28)
    at TLSSocket.socketErrorListener (node:_http_client:502:9)
    at TLSSocket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[2024-01-15 20:23:55.000] [info]  Requesting the feature list for en...
[2024-01-15 20:23:55.528] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 20:24:16.975] [info]  Omniverse Launcher 1.9.8 (production)
[2024-01-15 20:24:16.977] [info]  Argv: C:\Users\Administrator\AppData\Local\Programs\omniverse-launcher\NVIDIA Omniverse Launcher.exe
[2024-01-15 20:24:16.977] [info]  Crash dumps directory: C:\Users\Administrator\AppData\Roaming\omniverse-launcher\Crashpad
[2024-01-15 20:24:16.978] [info]  Start polling Launcher updates.
[2024-01-15 20:24:17.006] [debug] Reset current installer.
[2024-01-15 20:24:17.013] [info]  Running production web server.
[2024-01-15 20:24:17.024] [info]  HTTP endpoints listening at http://localhost:33480
[2024-01-15 20:24:17.025] [info]  HTTP endpoints listening at http://127.0.0.1:33480
[2024-01-15 20:24:17.028] [debug] Sharing: false
[2024-01-15 20:24:17.043] [info]  Started the Navigator web server on 127.0.0.1:34080.
[2024-01-15 20:24:17.407] [info]  Requesting the feature list for en...
[2024-01-15 20:24:17.663] [info]  Registered omniverse-launcher for Windows.
[2024-01-15 20:24:17.670] [info]  Registered omniverse for Windows.
[2024-01-15 20:24:17.750] [info]  Initialized.
[2024-01-15 20:24:17.977] [info]  Enabled features for en: { bugReports: false }
[2024-01-15 20:24:18.329] [info]  Logged in.
[2024-01-15 20:24:23.463] [warn]  Couldn't load featured components:  Error: Failed to fetch
[2024-01-15 20:24:25.107] [warn]  Couldn't load featured components:  Error: Failed to fetch
[2024-01-15 20:24:27.525] [warn]  Couldn't load featured components:  Error: Failed to fetch
[2024-01-15 20:24:31.940] [warn]  Couldn't load featured components:  Error: Failed to fetch
[2024-01-15 20:26:04.811] [warn]  Couldn't load featured components:  Error: Failed to fetch