Error 0x8013153b node js

it happens to me.

first try to use space or tab. in my first stop powershell

Download of vs_BuildTools.exe (1.4 MB) completed.
Hashes match.
Installing visualstudio2017buildtools...

is working…

guys if you use space or tab, and then work: this happens because you use the click-mouse in the PowerShell, don’t do this, sometimes is pausing the program [if is working, is a normal error, and it don’t cause nothing danger for completing the downloading]

but then I have a lot of white text.
the last stop is

[1968:0007][2021-08-24T19:47:57] Created a UnelevatedInstallerTelemetryDecorator

here the error you have.❌

for correct this error… do this!

• go to edge (or the browser you choose for download)
• go to download tab, where there is node-v14.17.5-x64.msi (for edge is CTRL+J)
• OPEN FILE
• CLICK REPAIR
  and that’s it

i will put some photos of final result if you need it:

final result SUCCESS✅

EDIT

After a while i have this, in the same powershell i have the first stop.

Chocolatey timed out waiting for the command to finish. The timeout
 specified (or the default value) was '2700' seconds. Perhaps try a
 higher `--execution-timeout`? See `choco -h` for details.
  visualstudio2017-workload-vctools may be able to be automatically uninstalled.
The upgrade of visualstudio2017-workload-vctools was NOT successful.
Error while running 'C:ProgramDatachocolateylibvisualstudio2017-workload-vctoolstoolsChocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 15/17 packages. 2 packages failed.
 See the log for details (C:ProgramDatachocolateylogschocolatey.log).

Upgraded:
 - chocolatey-dotnetfx.extension v1.0.1
 - kb3033929 v1.0.5
 - visualstudio2017buildtools v15.9.38.0
 - chocolatey-windowsupdate.extension v1.0.4
 - vcredist140 v14.29.30133
 - kb2999226 v1.0.20181019
 - visualstudio-installer v2.0.1
 - kb2919355 v1.0.20160915
 - chocolatey-core.extension v1.3.5.1
 - kb2919442 v1.0.20160915
 - chocolatey-visualstudio.extension v1.9.0
 - vcredist2015 v14.0.24215.20170201
 - dotnetfx v4.8.0.20190930
 - kb3035131 v1.0.3
 - python v3.9.6

Failures
 - python3 (exited 1603) - Error while running 'C:ProgramDatachocolateylibpython3toolschocolateyInstall.ps1'.
 See log for details.
 - visualstudio2017-workload-vctools (exited -1) - Error while running 'C:ProgramDatachocolateylibvisualstudio2017-workload-vctoolstoolsChocolateyInstall.ps1'.
 See log for details.

and the last thing is TYPE ENTER FOR EXIT — message on powershell

if you see the last message.

See "choco -h" for details.
so, i write it, in PowerShell.

i have this result, with a green message, in the end, with the version

This is a listing of all of the different things you can pass to choco.

Commands

 * list - lists remote or local packages
 * find - searches remote or local packages (alias for search)
 * search - searches remote or local packages (alias for list)
 * info - retrieves package information. Shorthand for choco search pkgname --exact --verbose
 * install - installs packages from various sources
 * pin - suppress upgrades for a package
 * outdated - retrieves packages that are outdated. Similar to upgrade all --noop
 * upgrade - upgrades packages from various sources
 * uninstall - uninstalls a package
 * pack - packages up a nuspec to a compiled nupkg
 * push - pushes a compiled nupkg
 * new - generates files necessary for a chocolatey package from a template
 * sources - view and configure default sources (alias for source)
 * source - view and configure default sources
 * config - Retrieve and configure config file settings
 * feature - view and configure choco features
 * features - view and configure choco features (alias for feature)
 * setapikey - retrieves, saves or deletes an apikey for a particular source (alias for apikey)
 * apikey - retrieves, saves or deletes an apikey for a particular source
 * unpackself - have chocolatey set itself up
 * version - [DEPRECATED] will be removed in v1 - use `choco outdated` or `cup <pkg|all> -whatif` instead
 * update - [DEPRECATED] RESERVED for future use (you are looking for upgrade, these are not the droids you are looking for)


Please run chocolatey with `choco command -help` for specific help on
 each command.

How To Pass Options / Switches

You can pass options and switches in the following ways:

 * Unless stated otherwise, an option/switch should only be passed one
   time. Otherwise you may find weird/non-supported behavior.
 * `-`, `/`, or `--` (one character switches should not use `--`)
 * **Option Bundling / Bundled Options**: One character switches can be
   bundled. e.g. `-d` (debug), `-f` (force), `-v` (verbose), and `-y`
   (confirm yes) can be bundled as `-dfvy`.
 * NOTE: If `debug` or `verbose` are bundled with local options
   (not the global ones above), some logging may not show up until after
   the local options are parsed.
 * **Use Equals**: You can also include or not include an equals sign
   `=` between options and values.
 * **Quote Values**: When you need to quote an entire argument, such as
   when using spaces, please use a combination of double quotes and
   apostrophes (`"'value'"`). In cmd.exe you can just use double quotes
   (`"value"`) but in powershell.exe you should use backticks
   (`` `"value`" ``) or apostrophes (`'value'`). Using the combination
   allows for both shells to work without issue, except for when the next
   section applies.
 * **Pass quotes in arguments**: When you need to pass quoted values to
   to something like a native installer, you are in for a world of fun. In
   cmd.exe you must pass it like this: `-ia "/yo=""Spaces spaces"""`. In
   PowerShell.exe, you must pass it like this: `-ia '/yo=""Spaces spaces""'`.
   No other combination will work. In PowerShell.exe if you are on version
   v3+, you can try `--%` before `-ia` to just pass the args through as is,
   which means it should not require any special workarounds.
 * **Periods in PowerShell**: If you need to pass a period as part of a
   value or a path, PowerShell doesn't always handle it well. Please
   quote those values using "Quote Values" section above.
 * Options and switches apply to all items passed, so if you are
   installing multiple packages, and you use `--version=1.0.0`, choco
   is going to look for and try to install version 1.0.0 of every
   package passed. So please split out multiple package calls when
   wanting to pass specific options.

Scripting / Integration - Best Practices / Style Guide

When writing scripts, such as PowerShell scripts passing options and
switches, there are some best practices to follow to ensure that you
don't run into issues later. This also applies to integrations that
are calling Chocolatey and parsing output. Chocolatey **uses**
PowerShell, but it is an exe, so it cannot return PowerShell objects.

Following these practices ensures both readability of your scripts AND
compatibility across different versions and editions of Chocolatey.
Following this guide will ensure your experience is not frustrating
based on choco not receiving things you think you are passing to it.

 * For consistency, always use `choco`, not `choco.exe`. Never use
   shortcut commands like `cinst` or `cup`.
 * Always have the command as the first argument to `choco. e.g.
   `choco install`, where `install` is the command.
 * If there is a subcommand, ensure that is the second argument. e.g.
   `choco source list`, where `source` is the command and `list` is the
   subcommand.
 * Typically the subject comes next. If installing packages, the
   subject would be the package names, e.g. `choco install pkg1 pkg2`.
 * Never use 'nupkg' or point directly to a nupkg file UNLESS using
   'choco push'. Use the source folder instead, e.g. `choco install
   <package id> --source="'c:folderwithpackage'"` instead of
   `choco install DoNotDoThis.1.0.nupkg` or `choco install DoNotDoThis
    --source="'c:folderwithpackageDoNotDoThis.1.0.nupkg'"`.
 * Switches and parameters are called simply options. Options come
   after the subject. e.g. `choco install pkg1 --debug --verbose`.
 * Never use the force option (`--force`/`-f`) in scripts (or really
   otherwise as a default mode of use). Force is an override on
   Chocolatey behavior. If you are wondering why Chocolatey isn't doing
   something like the documentation says it should, it's likely because
   you are using force. Stop.
 * Always use full option name. If the short option is `-n`, and the
   full option is `--name`, use `--name`. The only acceptable short
   option for use in scripts is `-y`. Find option names in help docs
   online or through `choco -?` /`choco [Command Name] -?`.
 * For scripts that are running automated, always use `-y`. Do note
   that even with `-y` passed, some things / state issues detected will
   temporarily stop for input - the key here is temporarily. They will
   continue without requiring any action after the temporary timeout
   (typically 30 seconds).
 * Full option names are prepended with two dashes, e.g. `--` or
   `--debug --verbose --ignore-proxy`.
 * When setting a value to an option, always put an equals (`=`)
   between the name and the setting, e.g. `--source="'local'"`.
 * When setting a value to an option, always surround the value
   properly with double quotes bookending apostrophes, e.g.
   `--source="'internal_server'"`.
 * If you are building PowerShell scripts, you can most likely just
   simply use apostrophes surrounding option values, e.g.
   `--source='internal_server'`.
 * Prefer upgrade to install in scripts. You can't `install` to a newer
   version of something, but you can `choco upgrade` which will do both
   upgrade or install (unless switched off explicitly).
 * If you are sharing the script with others, pass `--source` to be
   explicit about where the package is coming from. Use full link and
   not source name ('https://chocolatey.org/api/v2' versus
   'chocolatey').
 * If parsing output, you might want to use `--limit-output`/`-r` to
   get output in a more machine parseable format. NOTE: Not all
   commands handle return of information in an easily digestible
   output.
 * Use exit codes to determine status. Chocolatey exits with 0 when
   everything worked appropriately and other exits codes like 1 when
   things error. There are package specific exit codes that are
   recommended to be used and reboot indicating exit codes as well. To
   check exit code when using PowerShell, immediately call
   `$exitCode = $LASTEXITCODE` to get the value choco exited with.

Here's an example following bad practices (line breaks added for
 readability):

  `choco install pkg1 -y -params '/Option:Value /Option2:value with
   spaces' --c4b-option 'Yaass' --option-that-is-new 'dude upgrade'`

Now here is that example written with best practices (again line
 breaks added for readability - there are not line continuations
 for choco):

  `choco upgrade pkg1 -y --source="'https://chocolatey.org/api/v2'"
   --package-parameters="'/Option:Value /Option2:value with spaces'"
   --c4b-option="'Yaass'" --option-that-is-new="'dude upgrade'"`

Note the differences between the two:
 * Which is more self-documenting?
 * Which will allow for the newest version of something installed or
   upgraded to (which allows for more environmental consistency on
   packages and versions)?
 * Which may throw an error on a badly passed option?
 * Which will throw errors on unknown option values? See explanation
   below.

Chocolatey ignores options it doesn't understand, but it can only
 ignore option values if they are tied to the option with an
 equals sign ('='). Note those last two options in the examples above?
 If you roll off of a commercial edition or someone with older version
 attempts to run the badly crafted script `--c4b-option 'Yaass'
 --option-that-is-new 'dude upgrade'`, they are likely to see errors on
 'Yaass' and 'dude upgrade' because they are not explicitly tied to the
 option they are written after. Now compare that to the other script.
 Choco will ignore `--c4b-option="'Yaass'"` and
 `--option-that-is-new="'dude upgrade'"` as a whole when it doesn't
 register the options. This means that your script doesn't error.

Following these scripting best practices will ensure your scripts work
 everywhere they are used and with newer versions of Chocolatey.


Default Options and Switches

 -?, --help, -h
     Prints out the help menu.

 -d, --debug
     Debug - Show debug messaging.

 -v, --verbose
     Verbose - Show verbose messaging. Very verbose messaging, avoid using
       under normal circumstances.

     --trace
     Trace - Show trace messaging. Very, very verbose trace messaging. Avoid
       except when needing super low-level .NET Framework debugging. Available
       in 0.10.4+.

     --nocolor, --no-color
     No Color - Do not show colorization in logging output. This overrides
       the feature 'logWithoutColor', set to 'False'. Available in 0.10.9+.

     --acceptlicense, --accept-license
     AcceptLicense - Accept license dialogs automatically. Reserved for
       future use.

 -y, --yes, --confirm
     Confirm all prompts - Chooses affirmative answer instead of prompting.
       Implies --accept-license

 -f, --force
     Force - force the behavior. Do not use force during normal operation -
       it subverts some of the smart behavior for commands.

     --noop, --whatif, --what-if
     NoOp / WhatIf - Don't actually do anything.

 -r, --limitoutput, --limit-output
     LimitOutput - Limit the output to essential information

     --timeout, --execution-timeout=VALUE
     CommandExecutionTimeout (in seconds) - The time to allow a command to
       finish before timing out. Overrides the default execution timeout in the
       configuration of 2700 seconds. '0' for infinite starting in 0.10.4.

 -c, --cache, --cachelocation, --cache-location=VALUE
     CacheLocation - Location for download cache, defaults to %TEMP% or value
       in chocolatey.config file.

     --allowunofficial, --allow-unofficial, --allowunofficialbuild, --allow-unofficial-build
     AllowUnofficialBuild - When not using the official build you must set
       this flag for choco to continue.

     --failstderr, --failonstderr, --fail-on-stderr, --fail-on-standard-error, --fail-on-error-output
     FailOnStandardError - Fail on standard error output (stderr), typically
       received when running external commands during install providers. This
       overrides the feature failOnStandardError.

     --use-system-powershell
     UseSystemPowerShell - Execute PowerShell using an external process
       instead of the built-in PowerShell host. Should only be used when
       internal host is failing. Available in 0.9.10+.

     --no-progress
     Do Not Show Progress - Do not show download progress percentages.
       Available in 0.10.4+.

     --proxy=VALUE
     Proxy Location - Explicit proxy location. Overrides the default proxy
       location of ''. Available for config settings in 0.9.9.9+, this CLI
       option available in 0.10.4+.

     --proxy-user=VALUE
     Proxy User Name - Explicit proxy user (optional). Requires explicity
       proxy (`--proxy` or config setting). Overrides the default proxy user of
       ''. Available for config settings in 0.9.9.9+, this CLI option available
       in 0.10.4+.

     --proxy-password=VALUE
     Proxy Password - Explicit proxy password (optional) to be used with
       username. Requires explicity proxy (`--proxy` or config setting) and
       user name.  Overrides the default proxy password (encrypted in settings
       if set). Available for config settings in 0.9.9.9+, this CLI option
       available in 0.10.4+.

     --proxy-bypass-list=VALUE
     ProxyBypassList - Comma separated list of regex locations to bypass on
       proxy. Requires explicity proxy (`--proxy` or config setting). Overrides
       the default proxy bypass list of ''. Available in 0.10.4+.

     --proxy-bypass-on-local
     Proxy Bypass On Local - Bypass proxy for local connections. Requires
       explicity proxy (`--proxy` or config setting). Overrides the default
       proxy bypass on local setting of 'True'. Available in 0.10.4+.

     --log-file=VALUE
     Log File to output to in addition to regular loggers. Available in 0.1-
       0.8+.
Chocolatey v0.10.15

the most important thing is:

`Chocolatey v0.10.15`

chocolatey v.0.10.15 message

ok, let test if npm is installed

first at all write: npm -version

if return a version, you are fine!!!! 😊

now you can install from npm!

for example: me installing tailwindcss

• go to website of tailwindcss

• copy the npm code npm install tailwindcss

• go to vs code and paste it.

  PS C:UserslaaouDesktop> npm -version
  6.14.14
  PS C:UserslaaouDesktop> npm install tailwindcss
  npm WARN saveError ENOENT: no such file or directory, open ‘C:Userslaaoupackage.json’
  npm WARN enoent ENOENT: no such file or directory, open ‘C:Userslaaoupackage.json’
  npm WARN tailwindcss@2.2.7 requires a peer of autoprefixer@^10.0.2 but none is installed. You must install peer dependencies yourself.
  npm WARN laaou No description
  npm WARN laaou No repository field.
  npm WARN laaou No README data
  npm WARN laaou No license field.
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modulesfsevents):
  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»win32″,»arch»:»x64″})

• tailwindcss@2.2.7
  updated 1 package and audited 180 packages in 3.857s

17 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

PS C:UserslaaouDesktop>

• then try use npm fund if you are curious

Just experienced this issue, hung for 5-10 minutes then finished and prompted for closure. Hang in there I guess, to anybody else experiencing this.

Must be just the right time; here I was with it just under a day later. I’m pretty sure that’s what «NoUpdate» actually indicates; that it’s disabling the verbose output we’d been seeing on the screen previously. Without a message of any sort, it leaves one to wonder, though!

Update: Well, I hung in there, and after what felt like a lifetime*, it finally completed, ending with the Chocolatey Install/Upgrade job summary. So yeah, it’s basically just handling silent mode installation.

*Actually only like 25 minutes. I could see in Task Manager that PowerShell was actually chugging away; particularly disk usage, which suggested some installation was happening. And then Visual Studio Installer silently did something intensive, followed by «Windows® Installer», «Windows Modules Installer Worker», etc.) So basically, if nothing is visibly happening and you’re afraid it’s hung, just check task manager.

Some users have been reporting seeing the 0x8013153B error code whenever they try to open up the Microsoft Store. Looking at the hex code, the error can be translated into “The operation has been canceled”. The same error code is reported on Xbox consoles and certain Windows Phone models.

What causes the 0x8013153B error

After investigating the issue, it seems like the error can be caused by multiple factors. To make it easier, here’s a list of potential culprits that will trigger the 0x8013153B error:

• Internal Server Problem – Most of the time, when the store refuses to open with the 0x8013153B error, it’s signaling an internal server problem that has nothing to do with your machine. There have been occurrences in the past where the Microsoft Store crashed with the 0x8013153B error on all platforms (Windows, Windows Phone, and Xbox) for a full day.
• Corrupted Windows Store cache folder – There are instances where the 0x8013153B error was proven to be caused by internal corruption. As is turns out, the cache folder associated with Microsoft Store might trigger this particular issue if it becomes corrupted.
• Microsoft Store is configured to sideload apps – If the Microsoft Store is allowed to Sideload apps, the 0x8013153B error might occur because you have recently installed an application from a source that is less than legit.
• Windows phone bug – If you’re using a Windows Phone, you might be seeing this error due to a bug that is quite frequent on Microsoft Lumia models. Follow Method 4 for steps on getting around it.

How to fix the Error 0x8013153B

If you’re currently greeted by the 0x8013153B error whenever you try to open the Microsoft Store, this article will give you a list with the most efficient troubleshooting guides. Below you have a collection of methods that users in a similar situation have used in order to resolve the issue.

For the best results, follow the methods below in their order until you find a fix that is effective in your particular situation. If you’re encountering the issue on a Windows phone, jump straight to Method 5.

Checking if Microsoft Store is down

Before you start burning through the potential fixes below, it’s important to make sure that the issue is not server-side. Since the 0x8013153B error is primarily caused by a Microsoft problem that has nothing to do with the end client, we recommend that you verify the status of the Microsoft Store.

You can also verify if the Microsoft Store is working from a different device, but the better approach is to use a status check website like Is It Down or Outage. Another effective tactic is to follow the last posts on their Twitter account since they use it to announce repair sessions and outage times.

If you took the time to make the verifications and determined that the issue is caused by your computer, start following the methods below to resolve the 0x8013153B error.

Method 1: Using the Microsoft Store apps troubleshooter

If you want to take the easy route, you can’t go any simpler than to use the built-in Microsoft Store troubleshooter. This utility will scan your Microsoft Store application for any inconsistencies and apply appropriate repair strategies if the right scenario is met.

Some of the methods below are incorporated in the built-in troubleshooter so don’t skip this method if you’re looking to save time. Here’s a quick guide on how to run the Microsoft Store apps troubleshooter:

1. Press Windows key + R to open up a Run box. Next, type “ms-settings:troubleshoot” and press Enter to open the Troubleshooting tab of the Settings app.
   
2. In the Troubleshoot tab, scroll down to Find and fix other problems, click on Windows Store Apps and then click on Run the troubleshooter.
   
3. Wait until the initial scan is complete, then click on Apply this fix if any repair strategy is suggested.
4. Once the fix is applied, reboot your computer and see if the issue is resolved at the next startup. If you’re still struggling with the same error, continue with the next methods below.

Method 2: Resetting the Windows Store Cache

One of the first things that you should try if you’re dealing with the  0x8013153B error code is to reset the Windows Store cache folder to its original settings. If the application is failing due to underlying corruptions, this procedure will eliminate the bad files and restore the Windows Store app to its previous functionality.

Here’s a quick guide on how to reset the cache of the Windows Store app:

1. Press Windows key + R to open up a new Run window. Next, type “WSreset.exe” in the run box and press Enter to execute the command.
   
2. In the next several moments, you should see a black Command Prompt screen (until Windows manages to clear the cache of the Windows Store).
3. Depending on your Windows version, Windows Store will either start automatically or you’ll get a confirmation message saying “The cache for the Store was cleared. You can now browse the Store for apps.”. If the problem resulted from corruption present in the cache folder, the issue should now be fixed.

If you’re still seeing the 0x8013153B error code when you try to start Windows Store, continue down with the next steps below.

Method 3: Deleting the temp folder

Other users have managed to resolve the issue by deleting the contents of the temp folder and rebooting their machine. If Windows Store crashes due to a recently downloaded file that is not stored in the cache folder, this should be effective in solving the problem.

Follow the guide below to delete the temp folder in order to solve the 0x8013153B error:

1. Open File Explorer and navigate to C:Windowstemp and choose Yes at the UAC (User Account Control) prompt.
2. Select everything inside the temp folder, right-click on an item and choose to Delete to get rid of every temporary file.
   
3. Once the temp folder has been cleared, restart your computer and see if the issue has been resolved at the next startup.

If the issue is still not resolved, move down to the next method below.

Method 4: Enabling Microsoft Store Apps from the From Developers tab

If started getting the 0x8013153B error soon after you sideloaded a Microsoft Store app from outside the trusted zone, you might want to eliminate any apps that are not verified by Microsoft and see if the issue is resolved.

Thankfully, Microsoft included an option that allows the Store app to start with or without sideloaded apps. Some users have discovered that visiting the For developers tab inside the Settings menu them to resolve the 0x8013153B error. Here’s a quick guide on how to do this:

1. Press Windows key + R to open up a Run window. Then, type “ms-settings:windowsupdate” and hit Enter to open the Windows Update tab of the Settings app.
   
2. Next, use the left-hand tab to click on For developers.
3. Under Use developer features, click on Microsoft Store apps to prevent the store from sideloading apps.
   
4. Close the Settings app and reboot your computer.
5. At the next startup, open again Microsoft Store and see if the 0x8013153B error has been eliminated.

If you’re still prevented to open the Microsoft Store by the 0x8013153B error, continue down with Method 5.

Method 5: Turning Airplane Mode on while the page is loading 

The Windows Phone OS is far from perfect and this certainly contributed to its demise. Most Lumia models are plagued by the same problem – occasionally, Windows Store will refuse to open with the  0x8013153B error even when it’s functioning properly on other platforms. If you’re encountering this issue on a Windows 10 Phone model, you’ll need to occasionally jump through additional hoops in order to fix the 0x8013153B error.

Update: Some users have confirmed that this method can be recreated and actually works on PCs running on Windows 10.

Some users have discovered that closing the tab of Windows Store while it’s loading and enabling Airplane Mode will eventually get the Windows Store to open. Here’s a quick guide on how to do this:

1. Open Microsoft Store.
2. While the Microsoft tab is loading, close it’s tab.
3. Go to your phone’s settings (or use a shortcut) and enable Airplane mode.
4. Return to Microsoft Store and make it load again, then close the tab once more.
5. Disable Airplane mode and return to the Microsoft Store app.
6. This time it should load properly without the 0x8013153B error.

If you’re still seeing the 0x8013153B error when opening the store, move down to the next method below.

Method 6: Re-registering Microsoft Store from an elevated Powershell window

If none of the methods above have been effective, you might have better luck by going the manual route and using a Powershell command that registers the Microsoft Store app again and disables Development Mode.

Some users have reported that this procedure has been effective in allowing them to open the Store without the 0x8013153B error. Here’s a quick guide on how to do this:

1. Press Windows key + R to open up a Run window. Then, type “powershell“, press Ctrl + Shift + Enter and click Yes at the UAC prompt to open an elevated Powershell prompt.
   
2. In the elevated Powershell window, paste the following command and press Enter to run it:

   AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}

3. Wait until the command is processed. Depending on how many apps you have installed, this might take a while. Once the process is complete, open Windows Store again if it’s not opened automatically. You should no longer see the 0x8013153B error.

it happens to me.

first try to use space or tab. in my first stop powershell

Download of vs_BuildTools.exe (1.4 MB) completed.
Hashes match.
Installing visualstudio2017buildtools...

is working…

guys if you use space or tab, and then work: this happens because you use the click-mouse in the PowerShell, don’t do this, sometimes is pausing the program [if is working, is a normal error, and it don’t cause nothing danger for completing the downloading]

but then I have a lot of white text.
the last stop is

[1968:0007][2021-08-24T19:47:57] Created a UnelevatedInstallerTelemetryDecorator

here the error you have.❌

for correct this error… do this!

• go to edge (or the browser you choose for download)
• go to download tab, where there is node-v14.17.5-x64.msi (for edge is CTRL+J)
• OPEN FILE
• CLICK REPAIR
  and that’s it

i will put some photos of final result if you need it:

final result SUCCESS✅

EDIT

After a while i have this, in the same powershell i have the first stop.

Chocolatey timed out waiting for the command to finish. The timeout
 specified (or the default value) was '2700' seconds. Perhaps try a
 higher `--execution-timeout`? See `choco -h` for details.
  visualstudio2017-workload-vctools may be able to be automatically uninstalled.
The upgrade of visualstudio2017-workload-vctools was NOT successful.
Error while running 'C:ProgramDatachocolateylibvisualstudio2017-workload-vctoolstoolsChocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 15/17 packages. 2 packages failed.
 See the log for details (C:ProgramDatachocolateylogschocolatey.log).

Upgraded:
 - chocolatey-dotnetfx.extension v1.0.1
 - kb3033929 v1.0.5
 - visualstudio2017buildtools v15.9.38.0
 - chocolatey-windowsupdate.extension v1.0.4
 - vcredist140 v14.29.30133
 - kb2999226 v1.0.20181019
 - visualstudio-installer v2.0.1
 - kb2919355 v1.0.20160915
 - chocolatey-core.extension v1.3.5.1
 - kb2919442 v1.0.20160915
 - chocolatey-visualstudio.extension v1.9.0
 - vcredist2015 v14.0.24215.20170201
 - dotnetfx v4.8.0.20190930
 - kb3035131 v1.0.3
 - python v3.9.6

Failures
 - python3 (exited 1603) - Error while running 'C:ProgramDatachocolateylibpython3toolschocolateyInstall.ps1'.
 See log for details.
 - visualstudio2017-workload-vctools (exited -1) - Error while running 'C:ProgramDatachocolateylibvisualstudio2017-workload-vctoolstoolsChocolateyInstall.ps1'.
 See log for details.

and the last thing is TYPE ENTER FOR EXIT — message on powershell

if you see the last message.

See "choco -h" for details.
so, i write it, in PowerShell.

i have this result, with a green message, in the end, with the version

This is a listing of all of the different things you can pass to choco.

Commands

 * list - lists remote or local packages
 * find - searches remote or local packages (alias for search)
 * search - searches remote or local packages (alias for list)
 * info - retrieves package information. Shorthand for choco search pkgname --exact --verbose
 * install - installs packages from various sources
 * pin - suppress upgrades for a package
 * outdated - retrieves packages that are outdated. Similar to upgrade all --noop
 * upgrade - upgrades packages from various sources
 * uninstall - uninstalls a package
 * pack - packages up a nuspec to a compiled nupkg
 * push - pushes a compiled nupkg
 * new - generates files necessary for a chocolatey package from a template
 * sources - view and configure default sources (alias for source)
 * source - view and configure default sources
 * config - Retrieve and configure config file settings
 * feature - view and configure choco features
 * features - view and configure choco features (alias for feature)
 * setapikey - retrieves, saves or deletes an apikey for a particular source (alias for apikey)
 * apikey - retrieves, saves or deletes an apikey for a particular source
 * unpackself - have chocolatey set itself up
 * version - [DEPRECATED] will be removed in v1 - use `choco outdated` or `cup <pkg|all> -whatif` instead
 * update - [DEPRECATED] RESERVED for future use (you are looking for upgrade, these are not the droids you are looking for)


Please run chocolatey with `choco command -help` for specific help on
 each command.

How To Pass Options / Switches

You can pass options and switches in the following ways:

 * Unless stated otherwise, an option/switch should only be passed one
   time. Otherwise you may find weird/non-supported behavior.
 * `-`, `/`, or `--` (one character switches should not use `--`)
 * **Option Bundling / Bundled Options**: One character switches can be
   bundled. e.g. `-d` (debug), `-f` (force), `-v` (verbose), and `-y`
   (confirm yes) can be bundled as `-dfvy`.
 * NOTE: If `debug` or `verbose` are bundled with local options
   (not the global ones above), some logging may not show up until after
   the local options are parsed.
 * **Use Equals**: You can also include or not include an equals sign
   `=` between options and values.
 * **Quote Values**: When you need to quote an entire argument, such as
   when using spaces, please use a combination of double quotes and
   apostrophes (`"'value'"`). In cmd.exe you can just use double quotes
   (`"value"`) but in powershell.exe you should use backticks
   (`` `"value`" ``) or apostrophes (`'value'`). Using the combination
   allows for both shells to work without issue, except for when the next
   section applies.
 * **Pass quotes in arguments**: When you need to pass quoted values to
   to something like a native installer, you are in for a world of fun. In
   cmd.exe you must pass it like this: `-ia "/yo=""Spaces spaces"""`. In
   PowerShell.exe, you must pass it like this: `-ia '/yo=""Spaces spaces""'`.
   No other combination will work. In PowerShell.exe if you are on version
   v3+, you can try `--%` before `-ia` to just pass the args through as is,
   which means it should not require any special workarounds.
 * **Periods in PowerShell**: If you need to pass a period as part of a
   value or a path, PowerShell doesn't always handle it well. Please
   quote those values using "Quote Values" section above.
 * Options and switches apply to all items passed, so if you are
   installing multiple packages, and you use `--version=1.0.0`, choco
   is going to look for and try to install version 1.0.0 of every
   package passed. So please split out multiple package calls when
   wanting to pass specific options.

Scripting / Integration - Best Practices / Style Guide

When writing scripts, such as PowerShell scripts passing options and
switches, there are some best practices to follow to ensure that you
don't run into issues later. This also applies to integrations that
are calling Chocolatey and parsing output. Chocolatey **uses**
PowerShell, but it is an exe, so it cannot return PowerShell objects.

Following these practices ensures both readability of your scripts AND
compatibility across different versions and editions of Chocolatey.
Following this guide will ensure your experience is not frustrating
based on choco not receiving things you think you are passing to it.

 * For consistency, always use `choco`, not `choco.exe`. Never use
   shortcut commands like `cinst` or `cup`.
 * Always have the command as the first argument to `choco. e.g.
   `choco install`, where `install` is the command.
 * If there is a subcommand, ensure that is the second argument. e.g.
   `choco source list`, where `source` is the command and `list` is the
   subcommand.
 * Typically the subject comes next. If installing packages, the
   subject would be the package names, e.g. `choco install pkg1 pkg2`.
 * Never use 'nupkg' or point directly to a nupkg file UNLESS using
   'choco push'. Use the source folder instead, e.g. `choco install
   <package id> --source="'c:folderwithpackage'"` instead of
   `choco install DoNotDoThis.1.0.nupkg` or `choco install DoNotDoThis
    --source="'c:folderwithpackageDoNotDoThis.1.0.nupkg'"`.
 * Switches and parameters are called simply options. Options come
   after the subject. e.g. `choco install pkg1 --debug --verbose`.
 * Never use the force option (`--force`/`-f`) in scripts (or really
   otherwise as a default mode of use). Force is an override on
   Chocolatey behavior. If you are wondering why Chocolatey isn't doing
   something like the documentation says it should, it's likely because
   you are using force. Stop.
 * Always use full option name. If the short option is `-n`, and the
   full option is `--name`, use `--name`. The only acceptable short
   option for use in scripts is `-y`. Find option names in help docs
   online or through `choco -?` /`choco [Command Name] -?`.
 * For scripts that are running automated, always use `-y`. Do note
   that even with `-y` passed, some things / state issues detected will
   temporarily stop for input - the key here is temporarily. They will
   continue without requiring any action after the temporary timeout
   (typically 30 seconds).
 * Full option names are prepended with two dashes, e.g. `--` or
   `--debug --verbose --ignore-proxy`.
 * When setting a value to an option, always put an equals (`=`)
   between the name and the setting, e.g. `--source="'local'"`.
 * When setting a value to an option, always surround the value
   properly with double quotes bookending apostrophes, e.g.
   `--source="'internal_server'"`.
 * If you are building PowerShell scripts, you can most likely just
   simply use apostrophes surrounding option values, e.g.
   `--source='internal_server'`.
 * Prefer upgrade to install in scripts. You can't `install` to a newer
   version of something, but you can `choco upgrade` which will do both
   upgrade or install (unless switched off explicitly).
 * If you are sharing the script with others, pass `--source` to be
   explicit about where the package is coming from. Use full link and
   not source name ('https://chocolatey.org/api/v2' versus
   'chocolatey').
 * If parsing output, you might want to use `--limit-output`/`-r` to
   get output in a more machine parseable format. NOTE: Not all
   commands handle return of information in an easily digestible
   output.
 * Use exit codes to determine status. Chocolatey exits with 0 when
   everything worked appropriately and other exits codes like 1 when
   things error. There are package specific exit codes that are
   recommended to be used and reboot indicating exit codes as well. To
   check exit code when using PowerShell, immediately call
   `$exitCode = $LASTEXITCODE` to get the value choco exited with.

Here's an example following bad practices (line breaks added for
 readability):

  `choco install pkg1 -y -params '/Option:Value /Option2:value with
   spaces' --c4b-option 'Yaass' --option-that-is-new 'dude upgrade'`

Now here is that example written with best practices (again line
 breaks added for readability - there are not line continuations
 for choco):

  `choco upgrade pkg1 -y --source="'https://chocolatey.org/api/v2'"
   --package-parameters="'/Option:Value /Option2:value with spaces'"
   --c4b-option="'Yaass'" --option-that-is-new="'dude upgrade'"`

Note the differences between the two:
 * Which is more self-documenting?
 * Which will allow for the newest version of something installed or
   upgraded to (which allows for more environmental consistency on
   packages and versions)?
 * Which may throw an error on a badly passed option?
 * Which will throw errors on unknown option values? See explanation
   below.

Chocolatey ignores options it doesn't understand, but it can only
 ignore option values if they are tied to the option with an
 equals sign ('='). Note those last two options in the examples above?
 If you roll off of a commercial edition or someone with older version
 attempts to run the badly crafted script `--c4b-option 'Yaass'
 --option-that-is-new 'dude upgrade'`, they are likely to see errors on
 'Yaass' and 'dude upgrade' because they are not explicitly tied to the
 option they are written after. Now compare that to the other script.
 Choco will ignore `--c4b-option="'Yaass'"` and
 `--option-that-is-new="'dude upgrade'"` as a whole when it doesn't
 register the options. This means that your script doesn't error.

Following these scripting best practices will ensure your scripts work
 everywhere they are used and with newer versions of Chocolatey.


Default Options and Switches

 -?, --help, -h
     Prints out the help menu.

 -d, --debug
     Debug - Show debug messaging.

 -v, --verbose
     Verbose - Show verbose messaging. Very verbose messaging, avoid using
       under normal circumstances.

     --trace
     Trace - Show trace messaging. Very, very verbose trace messaging. Avoid
       except when needing super low-level .NET Framework debugging. Available
       in 0.10.4+.

     --nocolor, --no-color
     No Color - Do not show colorization in logging output. This overrides
       the feature 'logWithoutColor', set to 'False'. Available in 0.10.9+.

     --acceptlicense, --accept-license
     AcceptLicense - Accept license dialogs automatically. Reserved for
       future use.

 -y, --yes, --confirm
     Confirm all prompts - Chooses affirmative answer instead of prompting.
       Implies --accept-license

 -f, --force
     Force - force the behavior. Do not use force during normal operation -
       it subverts some of the smart behavior for commands.

     --noop, --whatif, --what-if
     NoOp / WhatIf - Don't actually do anything.

 -r, --limitoutput, --limit-output
     LimitOutput - Limit the output to essential information

     --timeout, --execution-timeout=VALUE
     CommandExecutionTimeout (in seconds) - The time to allow a command to
       finish before timing out. Overrides the default execution timeout in the
       configuration of 2700 seconds. '0' for infinite starting in 0.10.4.

 -c, --cache, --cachelocation, --cache-location=VALUE
     CacheLocation - Location for download cache, defaults to %TEMP% or value
       in chocolatey.config file.

     --allowunofficial, --allow-unofficial, --allowunofficialbuild, --allow-unofficial-build
     AllowUnofficialBuild - When not using the official build you must set
       this flag for choco to continue.

     --failstderr, --failonstderr, --fail-on-stderr, --fail-on-standard-error, --fail-on-error-output
     FailOnStandardError - Fail on standard error output (stderr), typically
       received when running external commands during install providers. This
       overrides the feature failOnStandardError.

     --use-system-powershell
     UseSystemPowerShell - Execute PowerShell using an external process
       instead of the built-in PowerShell host. Should only be used when
       internal host is failing. Available in 0.9.10+.

     --no-progress
     Do Not Show Progress - Do not show download progress percentages.
       Available in 0.10.4+.

     --proxy=VALUE
     Proxy Location - Explicit proxy location. Overrides the default proxy
       location of ''. Available for config settings in 0.9.9.9+, this CLI
       option available in 0.10.4+.

     --proxy-user=VALUE
     Proxy User Name - Explicit proxy user (optional). Requires explicity
       proxy (`--proxy` or config setting). Overrides the default proxy user of
       ''. Available for config settings in 0.9.9.9+, this CLI option available
       in 0.10.4+.

     --proxy-password=VALUE
     Proxy Password - Explicit proxy password (optional) to be used with
       username. Requires explicity proxy (`--proxy` or config setting) and
       user name.  Overrides the default proxy password (encrypted in settings
       if set). Available for config settings in 0.9.9.9+, this CLI option
       available in 0.10.4+.

     --proxy-bypass-list=VALUE
     ProxyBypassList - Comma separated list of regex locations to bypass on
       proxy. Requires explicity proxy (`--proxy` or config setting). Overrides
       the default proxy bypass list of ''. Available in 0.10.4+.

     --proxy-bypass-on-local
     Proxy Bypass On Local - Bypass proxy for local connections. Requires
       explicity proxy (`--proxy` or config setting). Overrides the default
       proxy bypass on local setting of 'True'. Available in 0.10.4+.

     --log-file=VALUE
     Log File to output to in addition to regular loggers. Available in 0.1-
       0.8+.
Chocolatey v0.10.15

the most important thing is:

chocolatey v.0.10.15 message

ok, let test if npm is installed

first at all write: npm -version

if return a version, you are fine!!!! 😊

now you can install from npm!

for example: me installing tailwindcss

• go to website of tailwindcss

• copy the npm code npm install tailwindcss

• go to vs code and paste it.

  PS C:UserslaaouDesktop> npm -version
  6.14.14
  PS C:UserslaaouDesktop> npm install tailwindcss
  npm WARN saveError ENOENT: no such file or directory, open ‘C:Userslaaoupackage.json’
  npm WARN enoent ENOENT: no such file or directory, open ‘C:Userslaaoupackage.json’
  npm WARN [email protected] requires a peer of [email protected]^10.0.2 but none is installed. You must install peer dependencies yourself.
  npm WARN laaou No description
  npm WARN laaou No repository field.
  npm WARN laaou No README data
  npm WARN laaou No license field.
  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modulesfsevents):
  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»win32″,»arch»:»x64″})

• [email protected]
  updated 1 package and audited 180 packages in 3.857s

17 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

PS C:UserslaaouDesktop>

• then try use npm fund if you are curious

Hello guys, today we will be discussing about a problem which is error code 0x8013153b. You may face it while installing Any new software-Program or you may even get to see this error if there is a missing DLL file. The most common reason is Corrupt .dll file or Registry files. Before effectively removing error code 0x8013153b issue, please run a free scan with SmartPCFixer.

Possible error code 0x8013153b error messages

«Runtime Error! Program [path]error code 0x8013153b. An application has made an attempt to load the C runtime library incorrectly. Please contact the application’s support team for more information.»
«Cannot find [PATH]error code 0x8013153b»
«Cannot start [APPLICATION]. A required component is missing: error code 0x8013153b. Please install [APPLICATION] again.»
«The file error code 0x8013153b is missing.»
«Windows could not start because error code 0x8013153b file is missing or corrupt.»
«[path]error code 0x8013153b is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media.»
«error code 0x8013153b Not Found»
«This application failed to start because error code 0x8013153b was not found. Re-installing the application may fix this problem.»
«The module error code 0x8013153b was loaded but the entry-point DllRegisterServer was not found. Make sure that error code 0x8013153b is a valid DLL or OCX file and then try again.»

How Can You Remove error code 0x8013153b Error Completely from Your System?

Method One: Fix error code 0x8013153b Error Automatically!

Highly Recommended: To scan, diagnose and repair your computer, use the Free Download recommended below. This tool is used to diagnose and repair errors that may be causing your computer to malfunction. SmartPCFixer is designed for computer users to enjoy a better digital life. It can detect, remove and block register error, dll error, common Trojan horses with ease. With this software, you can quickly and completely troubleshoot error code 0x8013153b errors. Follow the steps below and you can clear the error code 0x8013153b threat from the computer within minutes.

1. Download SmartPCFixer Now. (Free Download Now)

2. Click Quick Scan to Remove error code 0x8013153b problems completely.

3. Click Fix All to remove all computer error and speed up your PC automatically.

Method Two: Resolve error code 0x8013153b Error Manually!

You had better back up your important data before you trying to fix error code 0x8013153b

In most cases, if you want to solve error code 0x8013153b in a fast way, we recommend you to do a system restore for your PC.

1. Click Start Button and type system restore in the searching box.

2. Click System Restore and then follow the steps in the wizard to choose a restore point.

SmartPCFixer is highly Recommended..

Let SmartPCFixer Help you Now!

Related: Pc Upgrade Software,Error: 1297: 0x511,0x800ccc0f In Windows Mai…,Error C00d1059,Push Browser
Read More: ,0x50,0x00001d8,0x3ec,0x0002,0x00002e3