Why not running Experience Builder npm in administration mode fails?

[BrettLawson]

I no longer have administration rights to a machine on which Experience Builder is installed, but it I don't run command prompt as Administrator I get the error below and to contents of the log follow.

Is there a way around having to run as administrator?

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@6.13.4
3 info using node@v10.19.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle exb-client@1.0.0~prestart: exb-client@1.0.0
6 info lifecycle exb-client@1.0.0~start: exb-client@1.0.0
7 verbose lifecycle exb-client@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle exb-client@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Experience Builder\arcgis-experience-builder-1.0\client\node_modules\.bin;C:\Program Files (x86)\Windows Resource Kits\Tools\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\nodejs\;C:\Users\blawson\AppData\Local\Microsoft\WindowsApps;;C:\Users\blawson\AppData\Local\Programs\Microsoft VS Code\bin
9 verbose lifecycle exb-client@1.0.0~start: CWD: C:\Experience Builder\arcgis-experience-builder-1.0\client
10 silly lifecycle exb-client@1.0.0~start: Args: [ '/d /s /c',
10 silly lifecycle   'cross-env NODE_ENV=development webpack --mode development --watch' ]
11 silly lifecycle exb-client@1.0.0~start: Returned: code: 1  signal: null
12 info lifecycle exb-client@1.0.0~start: Failed to exec start script
13 verbose stack Error: exb-client@1.0.0 start: `cross-env NODE_ENV=development webpack --mode development --watch`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:198:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:198:13)
13 verbose stack     at maybeClose (internal/child_process.js:982:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid exb-client@1.0.0
15 verbose cwd C:\Experience Builder\arcgis-experience-builder-1.0\client
16 verbose Windows_NT 10.0.14393
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
18 verbose node v10.19.0
19 verbose npm  v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error exb-client@1.0.0 start: `cross-env NODE_ENV=development webpack --mode development --watch`
22 error Exit status 1
23 error Failed at the exb-client@1.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[BrettLawson · Accepted solution]

For anybody else who has this problem, have someone with administration privileges delete any custom widgets from [install directory]\client\dist\widgets folder and then restart the client npm script.

[Anneley_Hadland]

Hi I'm still getting this issue, I don't have any custom widgets, just the standard download. I am running cmd as Administrator. Please advise.