[Tex265AskWoody Plus]

Alex5723 wrote:

How to Hide Folders / Files from Search Results in Windows 10 https://www.top-password.com/blog/tag/exclude-folder-from-search-windows-10/%5B/quote%5D

Tex265 wrote:

Pls note I am not asking about Indexing, but how to make a setting to keep File Explorer itself from searching a specified folder or specific disk/partition.

Well, that’s what I thought also but the non-indexed folders don’t show up on the Taskbar Search, but the Taskbar Search offers to search File Explorer.  And anything in File Explorer seems to be searchable – files, folders, drives, partitions, extensions.

So still looking for an answer without having to password lock my system every time I step away for a few minutes.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

For my work I have legal and other docs on a second partition on a second hard drive.

I don’t want anyone who may have casual access to that computer to be able to “search”  that partition.

I can keep it from being indexed but the search in the Taskbar or in File Manager will search all drives and partitions on the computer.

There was an option in Windows 7 that at least could be checked to prevent searching within subfolders, but that option is not available in Windows 10 to set in advance and make it a permanent setting (vs per search).

So is there something I can set that would stop searching of designated disks, partitions, or folders?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

Under a previous posting “Chredge is Available Now” dated January 15, 2020, @b posted the following link on how we are suppose to be able to run Chredge and Edge side by side:

This article describes how to access Microsoft Edge Legacy (version 45 and earlier) after installing the new version of Microsoft Edge.
Access Microsoft Edge Legacy after installing the new version of Microsoft Edge

However there seemed to be issues with this working properly and the Group Policy settings were not to be found.

Do we have any further information of how to handle this “before” MS overinstalls Chredge?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

Running Win 10 x64 v1903  Updated thru January 2020

Upgraded to v1903 end of November 2019

My search box shows “Type here to search”

Build 2019.07.18.6227079

Have Local Account only, not Microsoft Account – could this matter?

 

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

1 user thanked author for this post.

CyGuy

[Tex265AskWoody Plus]

b wrote:

Have these caused any problem in the 8 months since you reported them at that other place (347 posts ago)?

I have never reported on this until now.  Only recently (November) moved from 1803 to 1903, but that is the day these Events started to show up and every shut down since.

Paul T wrote:

Look completely harmless to me – I would expect things not to start mid-shutdown

Never occurred in any previous version of Windows 10.

The known residual issue is that Windows Restore does not always automatically run like it use to.  May not be a bid deal but something is not functioning as it should.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

Assuming this is the 1909 fix that everyone has been waiting for, is there any other outstanding problem(s) with 1909?

Or will it finally be OK to update from 1903 to 1909?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

KYKaren wrote:

so it could happen that if three updates were listed on the WU screen and the user clicked on the “Download” button, all three of them would download/install one after the other without any more action from the user (in other words, not one by one with a “Download” button after each download/install)?

My experience is “Yes” they will sequentially download and install without any further Download button pressing option.

I have also noted this action on occasion  even when there are Defender updates involved. I think the difference is how long it has been since the Windows Updater ran and the user is pressing the Download button.  If very short time has passed since the Updater ran, the Defender updates may not provide the second Download button availability.

Possibly due to the fact that even with Group Policy set to 2 and Defender updates showing on the Window Updater screen, Defender updates will automatically install after a period of time with no user intervention (you can verify by looking View Update History).  If this happens, the Download button push is not re-installing them just removing their entry from the WU screen. If the time is short, they are actually being downloaded and installed at the same time as the others.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

KYKaren wrote:

Are you sure about this? When I use wushowhide to hide selected updates, it hides updates that had been heretofore already in the queue. I can then go back and initiate wushowhide again and it will show me the updates that are now hidden. So, this leads me to believe that they are hidden, BEFORE Windows Updates runs again on its schedule (which I have learned is 22 hours after the last time WU checked on its own).

I agree with your observations, but after all that (at least on my system) even though your selected updates show as hidden in wushowhide, they still appear on the Windows Update screen also.  I learned the hard way that as long as they still appear on the WU screen, they will download and install if you hit the Download button.  So you have to wait until they also no longer appear on the WU screen – which will be after the next time WU automatically checks.  Then the Download button will only download and install what the WU screen shows.  (the 22 hours is an approx and can vary several hours or more one way or the other).

KYKaren wrote:

I do know, though, that unhidden updates will not appear in the queue until WU runs again on its schedule. In other words, wushowhide had hidden them in order that they won’t appear (with a “Download” button, since the Group Policy Editor’s setting for Automatic Windows Updates is #2 “Notify download/install”) and unhiding them won’t make them appear on the Windows Update screen (with a “Download”button) until the next time WU checks on its own.

Correct.  Hiding updates basically works the same way as unhiding per above.

In the past pressing the Check for Updates button not only checked for updates but automatically installed them including an pending Feature updates so the button was rather useless.  Per Woody’s comment that action was reportedly changed with versions 1903 and 1909, but I have not seen confirmation that pressing the Check for Updates button will “refresh” the update queue after utilizing wushowhide as discussed.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

woody wrote:

If you’re running Win10 1903 or 1909, you don’t need to worry about the “Check for updates” link any more. Microsoft took the fangs out of it.

I asked about this a while back, but never received a definitive answer.

So can we feel free to utilize the “Check for updates” link with ver 1903 and 1909 vs having to wait for MS to run the Windows Updater?  eg: Feb Rollup came out and Group Policy setting 2 displayed updates but does not install; use wushowhide to hide select updates. Windows will not hide the selected updates until it runs again on its schedule, usually the next day.

Can we now feel free to utilize the “Check for updates” link/button to force Windows to update and hide those selected updates immediately?

Will that action also download and install ver 1909?  Or, will ver 1909 Feature Update appear but under the new install when you are ready link?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

1 user thanked author for this post.

KYKaren

[Tex265AskWoody Plus]

EP wrote:

Microsoft has released revised Intel Microcode updates this Thursday Jan. 30, 2020: KB4497165 for 1903/1909

I totally missed this item.  Also refer to gHacks.

Are we supposed to install?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

No problem, just wanted to clarify it is a recent problem related to 1903.

b wrote:

Did you try the script from there?

No have not.  That is beyond my comfort zone, but those that have say that it stops the Events from appearing but no one knows why other than some references in the Events themselves.

Doesn’t seem reasonable that MS expects users to create then have to run a script before every computer shut down.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

1 user thanked author for this post.

b

[Tex265AskWoody Plus]

Five (5) more months beyond 1903 EOL which will hopefully keep MS off my back for 18 months from now.

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

b wrote:

This article describes how to access Microsoft Edge Legacy (version 45 and earlier) after installing the new version of Microsoft Edge. Access Microsoft Edge Legacy after installing the new version of Microsoft Edge

Article says to Open Group Policy Editor and under Computer Configuration > Administrative Templates > Microsoft Edge Update > Applications  select “Allow Microsoft Edge Side by Side browser experience”.

I’m running Windows 10 Pro x64 v1903 and my Group Policy Editor does not show a Microsoft Edge Update category or any of the other path references.

Am I missing a Group Policy Add-in?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

@fernlady

I disabled the EOS Notify tasks (2) in the task scheduler yesterday and it worked for me.

In Task Manager, what is the path to follow to get to those specific tasks?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Tex265AskWoody Plus]

PK my question to you is that you have always insisted that SSU’s get installed first and exclusively.  Now let Windows decide?

Others including fernlady installed the SSU first then the other updates and got the same double restart, so same result.

Question though is: Why would MS bother to issue another new SSU in December, right after one in November, and right before the last Windows 7 update in January if it was only needed for the January – last ever update?  The install it last routine would mean the SSU was not needed for December only January – right?

Windows 10 Pro x64 v1903 and Windows 7 Pro SP1 x64

[Author]

Posts