I've been trying to update my server (Windows 10 Pro / 1903 Version) to version 2004 (KB3012973) through various Powershell scripts, but they all seem to apply no changes, at all, after restarting the machine.
Quite important to mention, I was successfully able to install previous updates through these scripts without any errors.
So, let me walk you through the process (PSWindowsUpdate):
First, looking for updates and using 'Install-WindowsUpdate' to install them all:
Rebooting the machine through either the script or manually by pressing on the 'Restart' button in the Start menu.
Letting the machine restart.... Then going into the Windows Update menu:
And viola! After restart, the windows version is just the same as it was before.
I have also tried running the script from the 'Searching, Downloading, and Installing Updates' tutorial by Microsoft, with no luck, as it seems.
I'd also like to note that oddly the update can be installed manually, by pressing the 'Install Now' button, which is sadly not what I'm looking for. As mentioned, the scripts have worked smoothly for previous updates.
Any help would be truly greatly appreciated!
Related
Trying to update my 32-bit Cygwin install on a Windows 10 64-bit fresh install and every setup-x86 I have tried fails with errors.
I had it all working on my old system, which was a Windows 7 upgrade to Windows 10. My 3rd party SDK with Cygwin plus an upgrade was installed a good few years ago while on Windows 7 then did the Windows 10 upgrade thing. I could still compile my code for an embedded processor device with no errors after that.
But Microsoft corrupted my system with the last update (December 2022) so my system was unbootable and irreparable by any of their troubleshooting Advanced methods.
So I put a new hard drive in and installed windows 10 from scratch.
Two weeks later I have reinstalled much software but now I am at my SDK re-install and cannot get any Cygwin version to download.
I have a 3rd party SDK which instructs me to install their Cygwin first (version 1.5.18) then remove some environment variables, then go to http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html and Follow the “Dead Simple Instructions" and go for "any version 2017 +".
After downloading the files I must copy the directory to my original install directory, thus upgrading the install.
I just cannot download anything though.
I went to that time machine page and was totally confused. I noticed they said "this is the last 32 bit install" on several places, so I tried clicking on all those setup-x86 links.
I tried running the downloaded setup-x86 files from the download directory but each one failed.
On most of the more recent setup-x86 files,(like 2.924) it shows a small blue square telling me Windows protected me etc. I click Run anyway and then it says "Cygwin is not supported on 32-bit windows".
So I tried earlier versions like 2.909 and they show the interface; I choose download, then choose the download directory ( a folder on my desktop) then I have tried both direct connection and use system proxy; then I select a mirror (tried all of them, I think) and it begins some action then stops with errors like:
"https:\cygwin.mirror.constant.com\x86\setup.ini line 12: The current ini file requires at least version 2.924 of setup. Please download a newer version from https://cygwin.com/setup-x86.exe"
But I have already tried 2.924 and it gives the "Cygwin is not supported on 32-bit windows" error!
With setup-x86-2.874.exe, it shows the interface etc. but in the mirror list all I see is http://update.setup.invalid.
With 2.774 it does the interface then "Unable to get setup.ini from 'my selected mirror url'.
Then I tried that page https://cygwin.com/install.html#unsupported, where I tried the circa urls and did these from an Administrator command line, as they say. No good- errors.
Under "Dead Simple Instructions"(no they are not) I followed the link to the machine top level snapshot index, but each link their only gives a plain text list of files- nothing downloadable!
Anyway, copied a url link and then at step 4 it says click for setup-x86. So I did but that blue windows protection square appears. I say run anyway but then it says "Cygwin is not supported on 32-bit windows"!
I am at my wits end! It all worked fine on my old system until Microsoft ruined it with their updates.
How can I get a newer cygwin update for my v1.5, s the 3rd party instructions say???
Aha! I believe I have finally got this to work.
I just found a new release of the instructions for the 3rd party software SDK. They mention version 2.9.0 as the new version they are moving to.
I cannot access their download but I went back and read the Cygwin Time Machine page carefully again (http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html).
Under "Dead Simple Instructions", I looked through the list of dates and versions (http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/index.html) and found 2.9.0-1; surely close enough, eh?
So I copied the URL shown there.
Step 4 Run setup-x86.exe downloaded the setup file and Itried it from an Admin CMD prompt, adding the -X and -D switches. It failed with the 32 bit error, as before.
OK so I read again and near the bottom of the page I spotted "Cygwin Setup Archive".
Ah... I went to the link provided there (http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/setup/setup.html) and found setup-x86-2.901.exe.
After it downloaded, I again used the command prompt to run this and an interface appeared.
I was able to choose the existing install directory, the temporary download directory and add the URL I had copied earlier.
It proceeded to get the list of packages correctly.
I then selected to view files that were installed but may need updating and clicked Next.
It all went correctly. Thanks to Doug who offered help already.
So there is a way to do this.
If anyone was looking for the solution, I found the answer in the Cygwin mailing list. You must launch the setup-x86.exe (setup-x86-2.924.exe) with the --allow-unsupported-windows option --site circa_URL arguments, much like the -X switch was used on prior legacy installers to disable signature checking. circa_URL here is a mirror of legacy repos for Cygwin, where http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/2022/11/23/063457 is the suggested url in the mailing listing post.
Apparently, if you are on a true x86, non-64-bit, Windows OS, this flag is not necessary, though I think the repo mirror may be required.
I got a new Surface Laptop 3. I typically use a MAC but need windows for a few things. I have been using parallels but decided to bite bullet and get real windows machine.
I use firebase and got firebase-tools installed and running fine. But when I tried to login (using firebase login for the CLI, I keep getting the error message as shown above: Assertion failed: new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309. I have used bash and powershell with same result. I also logged into a cmd prompt as administrator.
I have searched and searched and found a few things related to the clock and checked that. I also ran some filesystem checks etc. But nothing works. It all works OK in my Windows 10 envioronment under parallels on my MAC but this new laptop cant deal.
Can someone point me in the correct direction?
Looks like its an Ice Lake, Nodejs conflict of some sort. I was having this problem for months with my new HP spectre x360.
Seems it's been patched a few days ago in node: https://github.com/firebase/firebase-tools/issues/1772
I just updated my node install to 12.18.0 (I was on 12.16.1) and I'm no longer getting the error when I attempt firebase cli commands. Hopefully a node update will work for you as well: https://nodejs.org/en/download/
Update the Node!!!
in my case it was v14.4.0 and it was throwing the same error
new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309
and i updated the node to v14.8.0 and it worked fine.
I was having the same issue. After a loooooong search, I decided to try with WSL (Windows Subsystem for Linux). Once it finished, I installed node and firebase tools using it.
That is the only way that I found to solve this problem. Hope this will be helpful!
I had the same issue on my Windows10 x64 machine (Surface Pro 7) with one of my NodeJs projects. I've installed the latest surface pro fireware update (https://www.microsoft.com/en-us/download/details.aspx?id=100419) and updated to latest NodeJS 14.11.x Version (https://nodejs.org/en/download/current/).
now it works :)
for vm virtualbox win 10
I had the same issue on Windows 10. I simply synchronized the clock.
shut down Windows not restart
start vm (Windows)
go to clock settings "DATE & time"
set button called "Set time automatically" to on
set button called "Set time zone automatically" to on
There is a button called "Synchronize Your Clock" -> click button "Sync now"
And the issue got resolved
There is a hotfix version of Tortoise Git and my PC refuses to install it. It keeps saying Windows Explorer is running, even when it is not showing the Task Manager.
Is there any other way I can get this upgrade to install?
Update
I decided to start Windows 10 in Safe Mode so we can be sure that nothing is running. Yet it still would not perform the upgrade (with Administrator privileges):
I used Task Manager and I could not see gitdll.dll in the list of running processes.
1.download hotfixes
2.restart windows (don't open any apps after restart)
3.run Task Manager (from windows bar)
4.run hotfix from menu of Task Manager -- File -- Run new task
I have the same issue; I solved it by running:
listdlls64 -d "c:\Program Files\TortoiseGit\bin\gitdll.dll"
and used task manager to manually kill all processes that were using the dll, including explorer.exe. This seems entirely unnecessary but it's what worked for me.
Why so many processes (including LogonUI.exe, OpenWith.exe, splwow64.exe, etc.) attached to gitdll.dll, is unknown, and seems like an issue that can be solved. We know that explorer uses that dll, but you would think the installer/updater would expect that and be able to work around it.
In 2.10.x hotfixes there was a bug in the hotfix updater which was unable to offer a restart for replacing gitdll.dll during a restart cycle. A failure to replace this file caused lots of crashes (cf. https://tortoisegit.org/issue/3599).
Please download the full installer for TortoiseGit and install it (https://tortoisegit.org/download/; there might be a warning regarding a possible downgrade, this can be ignored).
Generally
The .MSI installer and newer hotfixes offer two options when installing:
Try to restart open processes - this might fail as described in https://stackoverflow.com/a/61026137/3906760 based on some third-party software.
Requiring no closing/restart of open programs but the replace the file on reboot. This should work in any case because the file is replaced before starting any programs using it.
I tried both types of installer:
Hotfix
Full
And both were refusing to work. I then occurred to me that all the icons were flashing on my desktop and it was stuck. This was consistent behaviour.
So I decided to switch of my Star Dock Fences:
Right-click Desktop and select Configure Fences:
Scroll-down to the bottom of the pop-up window and un-tick Enable Fences:
Close the window.
Now I was able to install the hot-fix. Interestingly the installer was only complaining about the Windows Explorer still running and did not list Fences.
I hope this helps any others who have struggles upgrading TortoiseGit.
I have successfully installed disabling AVIR and allowing the installer to close as much as it wants
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
So as I mentioned, I'm running windows 10.
When I first installed windows 10, visual studio community 2015 installed just fine. Then the licence expired so I wanted to reinstall it.
The installation just stops randomly... that it is stuck one one thing..
I also spotted a little connection between the bar saying 'Acquiring' and the second bar.. when the first bar is full, the installation gets stuck on installation of one current installing thing.
I don't know how to explain it though. It just never happened to me.
A screenshot wouldn't help and a video would be too long and boring.
I can't really tell if it is installing anything or not... I once let it install whole one day and it was stuck at the same thing that it was when I left home...
Is there any good explaination and or fix for that?
I finally found the solution for this problem!
I had to disable Windows Defender, because it was blocking the installation..
It was keeping the installation from running msi files.
To disable Windows Defender, follow the steps on this page: http://www.tenforums.com/tutorials/5918-windows-defender-turn-off-windows-10-a.html
Now the installation doesn't stop/isn't stuck on installing one thing :).
I hope I also helped the others that had the same problem before!