Closed OzBob closed 1 year ago
Same thing just happened to me 5 minutes ago. As I was writing this, PowerShell finally continued after hanging for a long, long time.
Same thing just happened to me 5 minutes ago. As I was writing this, PowerShell finally continued after hanging for a long, long time.
Same for me, but has not continued yet. But good to know it has a chance at continuing.
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.
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.
I have waiting for about 20 minutes and nothing happen. And then I check task manager and nothing to process. So I close it (Ctrl + C) and it has already finished. Maybe a little bug
Update: After a while I randomly switched between two of my open powershell windows and the script finished and closed its own window.
My install paused at this point:
[12cc:0011][2022-10-14T12:38:46] Package Microsoft.Net.4.8.FullRedist is not applicable: The current OS Version '10.0.22621.0' is not in the supported version range '[6.1.1,10.0.17763]'.
[12cc:0011][2022-10-14T12:38:46] Package Microsoft.VisualStudio.NuGet.PowershellBindingRedirect is not applicable: The current OS Version '10.0.22621.0' is not in the supported version range '[6.1,6.2)'.
Warning: [12cc:0011][2022-10-14T12:38:46] No previous catalog found at 'C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\1c66e466\catalog.previous.json'
[12cc:0010][2022-10-14T12:38:46] Adding packages from --add
[12cc:000d][2022-10-14T12:38:46] Planning graph selection
[12cc:000d][2022-10-14T12:38:46] Graph.PlanSelection completed in 2ms
[12cc:000d][2022-10-14T12:38:46] Building the required chain
[12cc:000d][2022-10-14T12:38:46] Committing graph selection
[12cc:000d][2022-10-14T12:38:46] Graph.CommitSelection completed in 1ms
[12cc:000d][2022-10-14T12:38:46] Updating graph selection
[12cc:000d][2022-10-14T12:38:46] Graph.UpdateSelection completed in 3ms
[12cc:000d][2022-10-14T12:38:46] Notifying VMs with the updated selections: GroupSelected - Microsoft.VisualStudio.Workload.VCTools Microsoft.VisualStudio.Component.VC.CoreBuildTools Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.VC.Redist.14.Latest Microsoft.VisualStudio.Component.Windows10SDK.19041 Microsoft.VisualStudio.Component.VC.CMake.Project Microsoft.VisualStudio.Component.TestTools.BuildTools Microsoft.VisualStudio.Component.VC.ASAN Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core Microsoft.VisualStudio.Component.Windows10SDK Microsoft.VisualStudio.Component.TextTemplating Microsoft.VisualStudio.Component.VC.CoreIde
[12cc:0018][2022-10-14T12:38:46] No restart manager available. Assuming no reboot required for instance state.
[12cc:0018][2022-10-14T12:38:46] No restart manager available. Assuming no reboot required for instance state.
[12cc:0004][2022-10-14T12:38:46] Creating a UnelevatedProductModifier to modify the following packages: Microsoft.VisualStudio.Product.BuildTools Microsoft.VisualStudio.Workload.MSBuildTools Microsoft.VisualStudio.Workload.VCTools Microsoft.VisualStudio.Component.Roslyn.Compiler Microsoft.Component.MSBuild Microsoft.VisualStudio.Component.CoreBuildTools Microsoft.VisualStudio.Component.Windows10SDK Microsoft.VisualStudio.Component.VC.CoreBuildTools Microsoft.VisualStudio.Component.VC.Tools.x86.x64 Microsoft.VisualStudio.Component.VC.Redist.14.Latest Microsoft.VisualStudio.Component.Windows10SDK.19041 Microsoft.VisualStudio.Component.VC.CMake.Project Microsoft.VisualStudio.Component.TestTools.BuildTools Microsoft.VisualStudio.Component.VC.ASAN Microsoft.VisualStudio.Component.TextTemplating Microsoft.VisualStudio.Component.VC.CoreIde Microsoft.VisualStudio.ComponentGroup.NativeDesktop.Core
[12cc:0004][2022-10-14T12:38:46] Created a UnelevatedProductModifier
[12cc:0004][2022-10-14T12:38:46] Decorating UnelevatedProductModifier with UnelevatedInstallerTelemetryDecorator
[12cc:0016][2022-10-14T12:38:46] Try to get the token in the 'in memory' cache for aka.ms
[12cc:0016][2022-10-14T12:38:46] Download requested: https://aka.ms/vs/15/release/channel
Warning: [12cc:0011][2022-10-14T12:38:46] The operation was canceled.
[12cc:000d][2022-10-14T12:38:46] Error 0x8013153b: [12cc:000d][2022-10-14T12:38:46] Could not update channel "https://aka.ms/vs/15/release/channel"
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Setup.Download.DownloadManagerAuthenticationProxy.<Download>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Setup.ChannelManager.<GetLatestChannelManifestAsync>d__88.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Setup.ChannelManager.<UpdateChannelManifestAsync>d__80.MoveNext()
Warning: [12cc:000d][2022-10-14T12:38:46] A task was canceled.
Warning: [12cc:000d][2022-10-14T12:38:46] Didn't find any channel feed.
[12cc:000d][2022-10-14T12:38:46] Try to get the token in the 'in memory' cache for aka.ms
[12cc:000d][2022-10-14T12:38:46] Download requested: https://aka.ms/vs/channels
[12cc:0028][2022-10-14T12:38:46] Attempting download 'https://aka.ms/vs/channels' using engine 'WebClient'
[12cc:0028][2022-10-14T12:38:46] Uri 'https://aka.ms/vs/channels' redirected to 'https://download.visualstudio.microsoft.com/download/pr/51407592-61e7-4034-bf60-bf620bf6e278/1b2855b1fa856e6ec65e543cb3e63bbd/channels.json'
[12cc:0028][2022-10-14T12:38:46] ManifestVerifier Result: NotSigned
[12cc:0028][2022-10-14T12:38:46] Manifest File: C:\Users\Reinier\AppData\Local\Temp\chocolatey\5h5vwyh0.json
[12cc:0028][2022-10-14T12:38:46] Download failed using WebClient engine. Microsoft.VisualStudio.Setup.Security.InvalidSignatureException: Manifest File: 5h5vwyh0.json
at Microsoft.VisualStudio.Setup.Download.DownloadManager.DownloadWithRetry(IDownloadEngine[] engines, Uri uri, Stream outputStream, ProgressUpdateCallback progress, CancellationToken cancellationToken, DownloadContext downloadContext, Boolean verifySignature)
[12cc:0028][2022-10-14T12:38:46] Sleeping 5000 milliseconds before retrying download.
Warning: [12cc:0028][2022-10-14T12:38:51] Failed to download channels file from https://aka.ms/vs/channels: Cannot access a closed file.
[12cc:0015][2022-10-14T12:38:51] Status changed to NoUpdate
Have only been waiting for a few minutes 😅
Check in Task Manager - Details if the setup.exe of the VisualStudio Installer is running - I waited for a while, stumbled across this thread, waited a bit longer while the PowerShell process was idle and seemingly nothing happened, but the VS build tools were installing in the background, took about 30 minutes then continued successfully!
Opened Administrator with a new window, then the old stucked window magical start to run and fininshed in seconds.
After 3 hours of wait, I pressed enter on the powershell and got this
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.
visualstudio2019-workload-vctools has been installed.
visualstudio2019-workload-vctools may be able to be automatically uninstalled.
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type refreshenv
).
The upgrade of visualstudio2019-workload-vctools was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\visualstudio2019-workload-vctools\tools\ChocolateyInstall.ps1'.
See log for details.
Chocolatey upgraded 18/19 packages. 1 packages failed. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Upgraded:
Failures
Missing status is the thing that makes us all itch. Just takes time. Monitoring the Powershell during this installation will show you minor blips in the processes used. You'll see the Dev Kit series pop a few times, maybe a few disk blips, then it will end with a few console hosts firing off and you're done. About 10 minutes from what I observed.
All I had to do was press ENTER key and it went ahead to show the next step which was to press ENTER again to Exit.
Just try and press enter first 🤷
Pressing enter solved it for me too -.-
After 3 hours of wait, I pressed enter on the powershell and got this
this worked for me :)). thank you a lot!!!!!!!
After 3 hours of wait, I pressed enter on the powershell and got this
same haha
I had VSCode open. Installer was hung for about 10 minutes. I closed VSCode and within 30 seconds installer came back to life and finished.
I had VSCode open. Installer was hung for about 10 minutes. I closed VSCode and within 30 seconds installer came back to life and finished.
same to me
I tested some things in this thread and it started doing some work again showing in the task manager. But stood still suddenly. Then i choose to press "enter" in the installation powershell. Then it abruptly gave some new lines of info and closed before i got to read it.
Why is this "Closed" when it is still an issue? Even if "Press Enter" or "Close VSCode" solve it, they are not obvious enough so this is still an issue. I closed the powershell window after getting tired of waiting, so I assume my installation is incorrect now. You should at least add a sufficiently visible note about "Press Enter if stuck on 'The operation was canceled' warnings for a long time" or "Close VSCode" somewhere in the whole process to inform users.
@anonghuser there's no "you should" in open source. If you feel your suggestion is the right approach, send a pull request.
@bnoordhuis sure, i could give it a try. where is the installer source? the only thing i'm finding is an old archived repo with electron-based installer, not the current msi one
It's in tools/msvs in this repo.
I am stuck here for years if I would have known that this was going to happen and I would have done it in the morning, and now I am stuck with a loading PowerShell for whole night
Just open the task manager and sort by disk usage, you will see things happening there.
About 5 minute wait for me. I saw zero disk activity, but it did finish up eventually.
As some others have remarked, the installation of Node can hang during the installation because VS Code is currently open. I closed VS Code and about 10 seconds later, the installation finished. Thought I'd add a comment here just to make others aware.
Version
v16.13.2
Platform
Windows NT 10.0.22000.0 x64
Subsystem
win11
What steps will reproduce the bug?
Win 11, VS2022 Preview installed, install win64 Node/npm
PowerShell step starts with:
Ends with:
The installer then hangs
How often does it reproduce? Is there a required condition?
Rerunning the 'install additional tools for node.js' solves the issue.
What is the expected behavior?
on 'Status changed to NoUpdate' the installer should exit
What do you see instead?
Installer hangs in the Powershell installer.
Additional information
No response