[BUG] npm ERR! code EINTEGRITY with Win-x64 msi but not Win-x86 msi

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

npm i -g @angular/cli generates lots of warnings about corrupted tarballs, and then fails with "npm ERR! code EINTEGRITY"

I've searched through all of the existing bugs about EINTGRITY and none of the solutions work for me

• npm cache clean --force
• npm cache verify
• delete my appdata npm and npm-cache
• can't delete package-lock.json because I don't have one
• npm i -g https://github.com/angular/angular-cli doesn't seem to work either
• npm config set package-lock false doesn't work

PS C:\Users\chuck\git> npm i -g @angular/cli
npm WARN tarball tarball data for @schematics/angular@https://registry.npmjs.org/@schematics/angular/-/angular-13.2.3.tgz (sha512-jloooGC7eco9AKxlIMMqFRptJYzZ0jNRBStWOp2dCISg6rmOKqpxbsHLtYFQIT1PnlomSxtKDAgYGQMDi9zhXw==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for @schematics/angular@https://registry.npmjs.org/@schematics/angular/-/angular-13.2.3.tgz (sha512-jloooGC7eco9AKxlIMMqFRptJYzZ0jNRBStWOp2dCISg6rmOKqpxbsHLtYFQIT1PnlomSxtKDAgYGQMDi9zhXw==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-jloooGC7eco9AKxlIMMqFRptJYzZ0jNRBStWOp2dCISg6rmOKqpxbsHLtYFQIT1PnlomSxtKDAgYGQMDi9zhXw== integrity checksum failed when using sha512: wanted sha512-jloooGC7eco9AKxlIMMqFRptJYzZ0jNRBStWOp2dCISg6rmOKqpxbsHLtYFQIT1PnlomSxtKDAgYGQMDi9zhXw== but got sha512-P+UD68uVka8jueOzf6aWNey9fwDf8Z4pANdB5vpRc69su8F3vQoV5xWSUs+s3xVsQbJb841rfP4tB1a5qXWiMA==. (1914981 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\chuck\AppData\Local\npm-cache\_logs\2022-02-10T07_16_34_029Z-debug-0.log

Expected Behavior

I expect the angular cli to be installed.

Steps To Reproduce

1. started with a fresh windows install
2. install node v16.14.0
3. open a powershell as administrator
4. npm i -g @angular/cli

Environment

• npm: 8.4.1
• Node.js: v16.14.0
• OS Name: Microsoft Windows 11 Home, 10.0.22000 Build 22000
• System Model Name: AMD Ryzen 7 5800x
• npm config:

PS C:\Users\chuck\git> npm config ls
; "builtin" config from C:\Users\chuck\AppData\Roaming\npm\node_modules\npm\npmrc

prefix = "C:\\Users\\chuck\\AppData\\Roaming\\npm"

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = C:\Users\chuck\git
; HOME = C:\Users\chuck
; Run `npm config ls -l` to show all defaults.

The report names no source file or test. Start by reproducing npm i -g @angular/cli with Node.js v16.14.0, npm 8.4.1, and Windows 11, then inspect the integrity-checking path and the supplied npm debug log. Done means the package installs without corrupted-tarball warnings or an EINTEGRITY failure.