Replies

Paul T wrote:

John, please don’t quote the whole post. Highlight the relevant section, then click Quote. cheers, Paul

 

Thanks Paul and I wasn’t aware you could do that prior to clicking the Quote. On some sports’ message boards I’m a member of,  you have to click Quote and then you can highlight what is relevant.

 

[Bob99]

John782 wrote:

Bob99 wrote:

Check the other Windows Update-related settings you may have in the registry and see if any of them have been changed from how you had them set.

If there have been no changes, you may wish to leave the update installed, since you didn’t say that you’ve had any issues since it installed.

If any of the settings have been changed away from what you had them set to, then you can return the settings to the way you had them and afterwards, proceed to uninstall the update should you choose to do so.

Basically, though, the choice is yours, and a matter of personal preference.

The basic intent of KB4023057 is to make it as trouble-free as possible to install the next Feature Update on your machine. It accomplishes the task through methods that can include changing update deferral settings and other changes to the way Windows Update can operate if it deems it appropriate. Because of this aspect of its potential behavior, some folks choose not to install it on their machine.

One thing it reportedly will do is to check you system drive (usually the C: drive) for enough space to ensure the update will be able to operate smoothly during the installation, which can be a good thing for anyone wishing to smoothly upgrade from one Feature Update to another, such as from 2004 or 20H2 to 21H1 or 21H2.

• This reply was modified 2 years, 7 months ago by Bob99.
• This reply was modified 2 years, 7 months ago by Bob99.
• This reply was modified 2 years, 7 months ago by Bob99.

Thanks, Bob. It deleted the setting where I had specified 2004. This has been deleted, “TargetReleaseVersionInfo”=”2004”

• This reply was modified 2 years, 7 months ago by John782.

Disregard. I wasn’t going through the proper way of getting to those settings. It is set to 2004.

[Bob99]

Bob99 wrote:

Check the other Windows Update-related settings you may have in the registry and see if any of them have been changed from how you had them set.

If there have been no changes, you may wish to leave the update installed, since you didn’t say that you’ve had any issues since it installed.

If any of the settings have been changed away from what you had them set to, then you can return the settings to the way you had them and afterwards, proceed to uninstall the update should you choose to do so.

Basically, though, the choice is yours, and a matter of personal preference.

The basic intent of KB4023057 is to make it as trouble-free as possible to install the next Feature Update on your machine. It accomplishes the task through methods that can include changing update deferral settings and other changes to the way Windows Update can operate if it deems it appropriate. Because of this aspect of its potential behavior, some folks choose not to install it on their machine.

One thing it reportedly will do is to check you system drive (usually the C: drive) for enough space to ensure the update will be able to operate smoothly during the installation, which can be a good thing for anyone wishing to smoothly upgrade from one Feature Update to another, such as from 2004 or 20H2 to 21H1 or 21H2.

• This reply was modified 2 years, 7 months ago by Bob99.
• This reply was modified 2 years, 7 months ago by Bob99.
• This reply was modified 2 years, 7 months ago by Bob99.

Thanks, Bob. It deleted the setting where I had specified 2004. This has been deleted, “TargetReleaseVersionInfo”=”2004”

• This reply was modified 2 years, 7 months ago by John782.

[John782]

I just checked the “View update history” and found that KB4023057 was installed with the January updates. I have 2004 Home and in the registry I have it set for 2004 only (as indicated in another thread). Do I need to to uninstall it in the Vuh?  Thanks.

• This reply was modified 2 years, 7 months ago by John782.

[John782]

PKCano wrote:

HKLM = HKEY_LOCAL_MACHINE

You are looking in the wrong place in the Registry. That’s why you can’t find what you are looking for.
Don’t use Search in the Registry. It has a tree structure like Explorer.
See the PICTURE – the second screenshot in #2286499.

PK, I did exactly what Susan said in the video, from the beginning, but I can’t navigate to  HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate because WindowsUpdate does not exist in that location. All the other Windows entries show (WcmSvc and WorkplaceJoin, etc.), as indicated on the video, but WindowsUpdate does not.

I don’t know if this happened after the 2004 upgrade by Microsoft, or if it had occurred earlier, or if I even ever had this option on my Windows’ Home Versions . I had no need to go into the Registry, for this purpose, until now so I don’t know what happened or when it occurred. All I know is that WindowsUpdates does not exist in the specified location.

I know how to add to the Registry, but I don’t know if all the values, etc. would work in this case?  I’m not sure either if downloading a registry batch file would work, and would add WindowsUpdates,  since I don’t have WindowsUpdates in that location now?  I think it would, but I’m not familiar with Registry batch files, or making new additions to the Registry. I have only changed some values in the past, but have never added too.

Thanks again for your assistance.

• This reply was modified 2 years, 7 months ago by John782.
• This reply was modified 2 years, 7 months ago by John782.

Susan Bradley wrote:

They have moved registry keys around during the versions, but they will respect other locations in the registry.  If you use the reg key download that should install it in a place that works.

Thanks Susan. I thought I knew a little bit about computers, but the more I read about things on here, it shows the less and less and less I know. Are you referring to “Registry Key Jumper” as the download?  Again I appreciate you and everyone else who is affiliated with this site and the expert advice given.

PKCano wrote:

I think you are looking in the wrong place in the Registry.
This is the location of the TRV settings.

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

See the second screenshot in #2286499.
The full path is shown by the top red arrow in the address bar in the screenshot.
The details are designated by the other red arrows.

Thanks PK but when I did a registry key search for HKLM, this is all that came up:  Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\HKLMEmailName

[John782]

John782 wrote:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ Microsoft/ Windows/Current User/WindowsUpdate

Paul, I was incorrect on the pathway. It’s [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate . Then it shows only
Default  REG_SZ   Date
TraylconStatus  REG_DWORD   0x00000001 (1)

My bad. Sorry for so much confusion. I should have called it a day, and pursued this tomorrow.

• This reply was modified 2 years, 8 months ago by John782.
• This reply was modified 2 years, 8 months ago by John782.
• This reply was modified 2 years, 8 months ago by John782.

Thanks b and Paul. I found the misbehaving App. It was Cortana. I never have used Cortana and had everything concerning it turned off when I was on 1909. As I had mentioned this had only occurred since the upgrade to 2004.  Since Cortana was in the Unknown folder, I decided to look at my settings for it. I found all settings were off with the exception of Cortana was in the startup menu. After I turned that off, I don’t have the message, ” Windows cannot access the specified device, path or file. You may not have the appropriate permission to access the item” when Windows starts up. Weird I haven’t had this issue with the Lenovo Yoga, but what is normal in life now?  So why shouldn’t I have weird stuff happening concerning my computer experiences.

1 user thanked author for this post.

b

[John782]

Paul T wrote:

TRV is set in the registry, not a folder. Use the REG files supplied by Susan to make the change.

John782 wrote:

I get this message every time I log

It seems you have lost an app from the MS store. Can you see what app is missing / not behaving?

cheers, Paul

Paul, I did a registry search and I found the WindowsUpdate under [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ Microsoft/ Windows/Current User/WindowsUpdate.  Any idea why that would be as I have not made any changes to either registry of my two PC’s?

• This reply was modified 2 years, 8 months ago by John782.

John782 wrote:

Paul T wrote:

TRV is set in the registry, not a folder. Use the REG files supplied by Susan to make the change.

John782 wrote:

I get this message every time I log

It seems you have lost an app from the MS store. Can you see what app is missing / not behaving?

cheers, Paul

My bad, Paul. It is not a folder but WindowsUpdate does not show, in the registry, under Windows on either PC.

I wonder if it because I was forced to download KB4023057, prior to Microsoft moving me to  2004, with their Windows November Feature Update?

 

Paul T wrote:

TRV is set in the registry, not a folder. Use the REG files supplied by Susan to make the change.

John782 wrote:

I get this message every time I log

It seems you have lost an app from the MS store. Can you see what app is missing / not behaving?

cheers, Paul

My bad, Paul. It is not a folder but WindowsUpdate does not show, in the registry, under Windows on either PC.

[John782]

I have the Windows 10 2004 Home version which was upgraded (Feature Upgrade November) by Microsoft from 1909 on my older Toshiba Satellite and Lenovo Yoga (September 2019 build date) and I was trying to do the TRV registry change to keep 2004. When I went through the procedures that Susan said, and looking at the video, once I got to the Windows folder, there was no WindowsUpdate folder? Can somebody help me with this?

Also after the upgrade to 2004, on the Toshiba Satellite, I get this message every time I log on: Windows cannot access the specified device, path or file. You may not have the appropriate permission to access the item. C:/ProgramFiles/WindowsApps/Microsoft.549981C3F10_2.2101.15643.0_x64_8wekyb3d8bbwe. I tried to take ownership of the file in properties and delete the file but it didn’t work.  In properties it shows as an Unknown File. I would appreciate any assistance concerning this as well?

Other than that, concerning the Toshiba PC,  since I did the free upgrade from W7 (back when) to W10 1909 and now 2004, I have had no other issues ( since installing W 10) other than the Windows Updates are extremely slower to install than W7 was, and they initially install 100% and then they have to re-install for some reason.

On the Yoga, I have not had any issues at all. It came with the W10 1903 build and then I upgraded to 1909 and then Microsoft upgraded me to 2004.

I appreciate what ya’ll do and the help I have received in the past. Thanks!

• This reply was modified 2 years, 8 months ago by John782.

PKCano wrote:

Go to Heidoc.net. The site IS https  https://www.heidoc.net/joomla/
Click on the Windows and Office ISO Download Tool

Download it to your desktop
Run it by double clicking on it.
Choose the ISO for the Windows *version, *Edition (Home or Pr0), and *bitedness (32 or 64 bit) that you want.
Download the ISO to your desktop.
Now you have several choices:
+ Double click on the ISO and mount OR right click on the ISO and “Open with” File Explorer. It will show up as another drive letter. You can install it on that computer by running setup.exe
+ You can copy/paste the ISO to a storage device (external USB HDD, for example) to be used later.
+ You can “burn” it to install media (DVD or bootable USB) to be used later.

Thank you, PKCano. You made it easy and simple. I downloaded the ISO file to the Desktop on both of my laptops. Then I copied the file and pasted it to a USB, that I had converted from a Fat32 format to a NTFS format. I had forgotten that when the USB is in the Fat32 format that you will always get a message that the file is too large even though you do have plenty of available space on the USB.

 

PKCano wrote:

If the .NET Preview is not causing any problems, leave it. It will be superseded by the next Patch Tuesday .Net Rollup.

Thanks,  PKCano. No issues noted so far.