Hi Wolfgang. Thanks for the suggestion. The computer wasn't in sleep mode. A normal press on the power button didn't have any effect. If it was in sleep mode or working normally, a normal press on the power button would usually have resumed it or put it in to sleep mode, respectively. This morning, it looked OK on the screen after the resume from hibernating but it was completely unresponsive to any stimulus, until the long press on the power button.

So windows had crashed. To my experience, this can happen with Vegas during rendering processes - when the pc goes into the power save mode. The settings should be set to off. Same may happen if the screen protection of windows becomes active during rendering. Should be disabled too.

That is certainly odd. Vegas shouldn't have anything that interferes with such a feature. Something went wrong during the hibernation process.... Tell you what, when you are ready to try it again, do a full uninstallation of Vegas update 2, you then install update 3, and afterwards restart your system..... Try that and see.

Hi Wolfgang and Steve. Thanks for your suggestions.

Yes, something weird happened, and my experience also says that it should not have been the upgrade of Vegas that did it. But I am very strict (obsessive?) about not allowing programs to update themselves, I have everything that I can locked down, so that updates only happen when I want them to occur. I am very confident that the only change made to the computer on Wednesday was the Vegas upgrade.

I finished my project yesterday, so today I did the upgrade again. The computer was not in the same state as it was in on Wednesday, as I had done upgrades to other programs after finishing the project. Today's upgrade of Vegas was done as close to the way that the upgrade on Wednesday was done as possible. I didn't uninstall Vegas before starting the upgrade. I'd have tried that path if the upgrade today didn't work or caused problems. After each of the two parts of the upgrades, I checked that the Search field had not been affected. After the second part of the upgrade, I hibernated the computer. It was OK after resuming it, and the Search field was not affected. A total shutdown, restart, hibernate, and resume all worked OK, with no locking up and no Search field issues. Vegas worked fine during all of the checking.

Whatever happened on Wednesday has not reoccurred today, which is good news. But it does reinforce my habit of taking image backups of my C: drive throughout the monthly update cycle I have for the computer.

Hopefully, nobody else runs in to problems after Upgrade 3 is applied.

Well, glad that everything is running smoothly for you now after the update. And speaking about allowing programs to update themselves, that is something that i am always strongly against...... Especially Windows Automatic updates, which i detest, because it can totally ruin your smooth editing workflow that you spent months refining.

Thanks Steve. I've got Windows and Edge Updates mostly tamed, by having my WiFi connection set to metered. It doesn't stop them all from happening by themselves, but the major ones generally have to be given permission to be downloaded.

I'm right there with you on keeping my system locked down (and probably as obsessive), where I've not only set the regular settings to prevent Windows updates (which have proven to be useless when Microsoft wants you to update), I've gone so far as putting in additional firewall settings, group policies and user policies to prevent updates, and it wasn't surprising to learn that my Windows Build version is just one under you. All that is just to say, we've probably had our fair share of terrible experiences resulting from updates that makes us so hesitant to let them run on their own.

In any case, I just wanted to ask about your second experience with upgrading to version 3, recognizing that your computer was not in the same state as when you did the first upgrade, I just wanted to confirm that when you tested the hibernation, Vegas was left open similarly to the time after the first upgrade with project and all?

I may be bias, but I would've suspected that some part of the version 3 upgrade may have potentially triggered a Visual studio library to be upgraded for the AI features or something and giving Microsoft a way of sneaking some other update files in to cause the search malfunction (admittedly I'm just being overdramatic at this point), it's still concerning to say the least. While updating other software on your PC could theoretically have some effect on associated files to somehow prevent a reoccurring Windows search function crash, I'm now all the more weary about upgrading after hearing your story, mainly because I'm mid-project and wouldn't want to risk anything. But, please let me know about the hibernation post second upgrade, if it was done with Vegas open again as well or if it was just put into hibernation without Vegas open.

Hi EditorCP. I did the hibernation test with Vegas open and a project loaded, as was the case before when the lock up occurred. I tried to have everything in as close to the first state as possible, acknowledging that the overall computer state was different the second time. The test hibernate wasn't overnight, but just for a few minutes. But I figured that shouldn't matter. I didn't have Vegas active when I hibernated last night, and it resumed fine this morning. So fingers crossed that the problem was a one-off and hopefully it'll just affect me. It wasn't a major issue rolling back a few days, as I'd not done any other upgrades since taking the image backup I used for the restore.

@Raymond-Mardle

The computer is running Windows 10 22H2 Build 19045.4170,

Mine too.

The timing of your upgrade installation, and problems after hibernating may be unrelated, except that they happened about the same time. post hoc ergo propter hoc

My Windows 10 machine slowed to a crawl the same day as yours! Everything from missing shell icons to the endless security scan (green bar), inability to delete files and numerous unresponsive applications, hard reboots didn't help.

Fortunately, these exact symptoms were not unfamiliar to me, and the same solution worked again.

I uninstalled Windows Security Update KB5035845, which had installed on 4/11/2024, and everything was back to normal on reboot.

That security update has since reinstalled itself today without apparent further issues.