Replies

Identity Theft Day? Does that mean I need to go steal someone’s identity to celebrate?

In the article, there was concern about adjusting links to the Settings app from the Start menu. Use the Windows key and the letter ‘i’ as in India to go straight to the Settings app, no Start menu needed.

I just tested hiding an update on 24h2 with wushowhide.cab and it works properly.

2 users thanked author for this post.

Tex265, Paul T

I had this same ‘not applicable’ issue on the domain controllers on my network. After a few guesses, I got the fix. The problem is that your delay of twenty-one days (mine was thirty) makes the MSU think that its patch is not yet applicable. The fix is to set that down to one day and then run the MSU. Note that the MSU does not care about the setting that says whether or not to delay quality updates, it only cares about the number of days. Also note where your group policy will apply for the number of days setting. In my case, I make the thirty day setting I use in the default domain policy. I do not want to change that group policy because I do not want every machine in my domain to apply April updates. The way I worked around it for my domain controllers was to make the following regedit on my domain controller:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DeferQualityUpdatesPeriodInDays"=dword:00000001

Then run the MSU and reboot when prompted. Once the machine comes back up, then do gpupdate/force to re-apply the default domain policy setting of having your twenty-one (thirty in my case) days of cushion.

I keep my Outlook on the semi-annual channel, so I must not have not yet gotten whatever update took away this option. Digging around I found the underlying registry entry for this is

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Preferences]
“ReopenWindowsOption”=dword:00000000

For that dword, set 0 to get a prompt, set 1 to never reopen, or set 2 to always reopen.

So, no guarantees, but you can try making the registry entry and seeing if you can get the behavior that you’re looking for.

4 users thanked author for this post.

SeizeDub, windbg, lmacri, Drcard:))

You will need a USB flash drive for what I would recommend. If you do not already have it, download the portable EXE for Rufus from https://rufus.ie/en/ . Download the Ultimate Boot CD (UBCD) from https://www.ultimatebootcd.com/ . Insert your flash drive, run Rufus as an administrator, use the ‘select’ button to browse to your UBCD ISO file and write that out to the flash drive. Now, choose which way to proceed. The safe approach will be to remove your known good SSD and swap in this questionable SSD. The less safe approach would be to have both attached. Either way, boot from the USB flash drive to get to the main UBCD screen, choose the HDD/Drive Wiping option, and then use one of the programs there. Of the options that are available, Active@ KillDisk Free Edition looks like the one to pick. Then select your SSD to wipe. This is why I said the safer thing was to swap drives, so that you are guaranteed that you are not wiping your known good disk. Once you are absolutely sure that you are not wiping your known good drive, wipe the questionable drive. Finish, shutdown, get your PC back to stable one and bring it back up. Reconnect the questionable SSD via that USB connection, and see if everything looks cleared out.