A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Missing Startup progs after WU



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old March 14th 19, 03:40 PM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 634
Default Missing Startup progs after WU

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.

I ran Nirsoft's AutoRuns and these missing programs were now showing
with .lnk file entries, instead of .exe like most of the hundreds of
other entries.

Also: while in AutoRuns I saved the .arn file as a precaution and
deleted a few entries which seemed identical duplicates. After a PC
restart the missing progs were still missing. I re-loaded my .arn file.
On then looking in my Startup folders, which probably had around ten
entries, to my dismay I found they were all missing.

I'm about to search for backups of
C:\ProgramData\Microsoft\Windows\Start Menu
and
C:\Users\terry\AppData\Roaming\Microsoft\Windows\S tart Menu
but meanwhile any insights please?

Terry, UK
Ads
  #2  
Old March 14th 19, 06:53 PM posted to alt.comp.os.windows-10
VanguardLH[_2_]
external usenet poster
 
Posts: 9,980
Default Missing Startup progs after WU

Terry Pinnell wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.

I ran Nirsoft's AutoRuns and these missing programs were now showing
with .lnk file entries, instead of .exe like most of the hundreds of
other entries.

Also: while in AutoRuns I saved the .arn file as a precaution and
deleted a few entries which seemed identical duplicates. After a PC
restart the missing progs were still missing. I re-loaded my .arn file.
On then looking in my Startup folders, which probably had around ten
entries, to my dismay I found they were all missing.

I'm about to search for backups of
C:\ProgramData\Microsoft\Windows\Start Menu
and
C:\Users\terry\AppData\Roaming\Microsoft\Windows\S tart Menu
but meanwhile any insights please?

Terry, UK


The .lnk files are, well, files which normally are referred to as
shortcuts. The entries in your Start menu are .lnk files: shortcuts to
where are the real programs.

In the startup entries for programs that are now .lnk files, look at
where is the .lnk file. Then, in Windows Explorer, go to that folder
where is the .lnk file, or to where the startup entry pointed. If there
is no .lnk file there, that's your problem: there is no shortcut there
to find to load the program it would be pointing to. If there is a .lnk
file there, double-click on it to see if the shortcut works. If the
shortcut does not work, edit the shortcut to see to where it points for
the program it is supposed to load.
  #3  
Old March 14th 19, 08:08 PM posted to alt.comp.os.windows-10
Monty
external usenet poster
 
Posts: 550
Default Missing Startup progs after WU

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.


That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379

  #4  
Old March 14th 19, 11:28 PM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 375
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.


That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379


I've got one machine still on 1803. MS does not seem to want to offer
it 1809.
--

Regards,

Eric Stevens
  #5  
Old March 15th 19, 06:31 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 8,777
Default Missing Startup progs after WU

Eric Stevens wrote:
On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.

That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379


I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


In the Settings Wheel : Update and Security, what does
the Windows Update History tab show ? Does it show an update
which is failed, and blocks other updates ? You can have
a "log jam", where WU is trying to get some older update
to install, and this prevents 1809 from being considered.

If you get the failed update (which is not followed by any
success entry with the same number), then you can go to
catalog.update.microsoft.com and get the MSU for that KB
via manual download. Double click it and install it.

There is usually sufficient logic (and wsusscn content) for
an MSU to figure out whether it's relevant or not. I've never
seen a case where trying to use an MSU caused a problem.

I found the "need to install 1809" was pretty aggressive
a couple days ago, and an install I didn't particularly want
updated, started to update on this machine. The cleanup
behavior is there, to "move on to the next thing".

If you've been messing around with "streams" and using the
Long Term business stream (whatever that's called today",
maybe you could break it that way. Also, in the past,
if you manually reverted the OS version (made the OS
loot C:\Windows.old and put things back), that also
functions as a "manual barrier" to upgrading. And running
a Repair Install by executing Setup.exe might be the simplest
way to move forward again.

By knowing things you've done to the OS along the way,
there may be some hint as to why.

I've also noticed, that a number of items referenced by
people on the web, concerning the Registry, and ways to
control this behavior, don't actually work. And a ton of
stuff that worked at one time, is just left there as
a "grave yard" of registry entries. Even if you did find
some registry entries that didn't match what it told
you to do on the web, it could be the OS isn't even paying
attention to those now. I used to look at those, when the
Insider Edition threw a wobbly, and fiddling that stuff as
instructed, didn't do a thing. The Insider is constantly doing
Upgrades, and is an excellent test vehicle for such.

Paul
  #6  
Old March 15th 19, 09:27 AM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 634
Default Missing Startup progs after WU

Eric Stevens wrote:

On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.


That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379


I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


Same here.

Terry, East Grinstead, UK
  #7  
Old March 15th 19, 09:30 AM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 375
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 02:31:15 -0400, Paul
wrote:

Eric Stevens wrote:
On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.
That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379


I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


In the Settings Wheel : Update and Security, what does
the Windows Update History tab show ? Does it show an update
which is failed, and blocks other updates ? You can have
a "log jam", where WU is trying to get some older update
to install, and this prevents 1809 from being considered.

!803 is all it knows about. There is no evidence of problems with
updates. It hasn't been used much for several weeks and when I started
it up to read its history it gave me a list of three updates for 1803
which it is right now downloading and going to install. There was no
mention of 1809. I'll wait to see what the future holds.

If you get the failed update (which is not followed by any
success entry with the same number), then you can go to
catalog.update.microsoft.com and get the MSU for that KB
via manual download. Double click it and install it.

There is usually sufficient logic (and wsusscn content) for
an MSU to figure out whether it's relevant or not. I've never
seen a case where trying to use an MSU caused a problem.

I found the "need to install 1809" was pretty aggressive
a couple days ago, and an install I didn't particularly want
updated, started to update on this machine. The cleanup
behavior is there, to "move on to the next thing".

If you've been messing around with "streams" and using the
Long Term business stream (whatever that's called today",
maybe you could break it that way. Also, in the past,
if you manually reverted the OS version (made the OS
loot C:\Windows.old and put things back), that also
functions as a "manual barrier" to upgrading. And running
a Repair Install by executing Setup.exe might be the simplest
way to move forward again.

By knowing things you've done to the OS along the way,
there may be some hint as to why.

I've also noticed, that a number of items referenced by
people on the web, concerning the Registry, and ways to
control this behavior, don't actually work. And a ton of
stuff that worked at one time, is just left there as
a "grave yard" of registry entries. Even if you did find
some registry entries that didn't match what it told
you to do on the web, it could be the OS isn't even paying
attention to those now. I used to look at those, when the
Insider Edition threw a wobbly, and fiddling that stuff as
instructed, didn't do a thing. The Insider is constantly doing
Upgrades, and is an excellent test vehicle for such.

Paul

--

Regards,

Eric Stevens
  #8  
Old March 15th 19, 09:37 AM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 634
Default Missing Startup progs after WU

Paul wrote:

Eric Stevens wrote:
On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.
That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379


I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


In the Settings Wheel : Update and Security, what does
the Windows Update History tab show ? Does it show an update
which is failed, and blocks other updates ? You can have
a "log jam", where WU is trying to get some older update
to install, and this prevents 1809 from being considered.

If you get the failed update (which is not followed by any
success entry with the same number), then you can go to
catalog.update.microsoft.com and get the MSU for that KB
via manual download. Double click it and install it.

There is usually sufficient logic (and wsusscn content) for
an MSU to figure out whether it's relevant or not. I've never
seen a case where trying to use an MSU caused a problem.

I found the "need to install 1809" was pretty aggressive
a couple days ago, and an install I didn't particularly want
updated, started to update on this machine. The cleanup
behavior is there, to "move on to the next thing".

If you've been messing around with "streams" and using the
Long Term business stream (whatever that's called today",
maybe you could break it that way. Also, in the past,
if you manually reverted the OS version (made the OS
loot C:\Windows.old and put things back), that also
functions as a "manual barrier" to upgrading. And running
a Repair Install by executing Setup.exe might be the simplest
way to move forward again.

By knowing things you've done to the OS along the way,
there may be some hint as to why.

I've also noticed, that a number of items referenced by
people on the web, concerning the Registry, and ways to
control this behavior, don't actually work. And a ton of
stuff that worked at one time, is just left there as
a "grave yard" of registry entries. Even if you did find
some registry entries that didn't match what it told
you to do on the web, it could be the OS isn't even paying
attention to those now. I used to look at those, when the
Insider Edition threw a wobbly, and fiddling that stuff as
instructed, didn't do a thing. The Insider is constantly doing
Upgrades, and is an excellent test vehicle for such.

Paul


Thanks Paul. I used my nightly backup of
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp
to replace those mysteriously lost entries and after a couple of reboots
things seem to be OK.

Why would WU not be updating some PCs to 1809 and should I be worried or
relieved that mine is one of them?

FWIW here's my recent Quality update history:

Quality Updates (21)

2019-03 Cumulative Update for Windows 10 Version 1803 for x64-based
Systems (KB4489868)
Successfully installed on 14/03/19
2019-03 Security Update for Adobe Flash Player for Windows 10 Version
1803 for x64—based Systems
Successfully installed on 14/03/19
2019-02 Update for Windows 10 Version 1803 for x64—based Systems
(KB4023057)
Successfully installed on 01/03/19
2019-02 Update for Windows 10 Version 1803 for x64—based Systems
(KB4023057)
Successfully installed on 15/02/19
2019-02 Cumulative Update for Windows 10 Version 1803 for x64—based
Systems (KB4487017)
Successfully installed on 13/02/19
2019-02 Security Update for Adobe Flash Player for Windows 10 Version
1803 for x64-based Systems
Successfully installed on 13/02/19
2018-10 Update for Windows 10 Version 1803 for x64-based Systems
(KB4100347)
Successfully installed on 06/02/19
2018-10 Update for Windows 10 Version 1803 for x64—based Systems
(KB4100347) (12)
Last failed install attempt on 04/02/19 - 0x80240034
2019-01 Update for Windows 10 Version 1803 for x64-based Systems
(KB4023057)
Successfully installed on 18/01/19
2018-11 Update for Windows 10 Version 1803 for x64-based Systems
(KB4023057) (2)
Last failed install attempt on 18/01/19 - 0x80070643
2019-01 Security Update for Adobe Flash Player for \Windows 10 Version
1803 for x64-based System
Successfully installed on 10/01/19
2019-01 Cumulative Update for Windows 10 Version 1803 for x64-based
Systems (KB4480966)
Successfully installed on 10/01/19

Terry, East Grinstead, UK
  #9  
Old March 15th 19, 09:58 AM posted to alt.comp.os.windows-10
rp[_2_]
external usenet poster
 
Posts: 32
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 12:28:46 +1300, Eric Stevens wrote:

I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


Soon Microsoft will bring back memories. I used to service ICL 1903
mainframes in the late '80s/early'90s.

--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail rpont (at) gmail (dot) com


  #10  
Old March 15th 19, 10:37 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 8,777
Default Missing Startup progs after WU

Eric Stevens wrote:

!803 is all it knows about. There is no evidence of problems with
updates. It hasn't been used much for several weeks and when I started
it up to read its history it gave me a list of three updates for 1803
which it is right now downloading and going to install. There was no
mention of 1809. I'll wait to see what the future holds.


You might be surprised to find it downloading 1809,
after the other update install.

Paul
  #11  
Old March 15th 19, 10:48 AM posted to alt.comp.os.windows-10
rp[_2_]
external usenet poster
 
Posts: 32
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 09:58:17 +0000 (GMT), rp wrote:

I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


Soon Microsoft will bring back memories. I used to service ICL 1903
mainframes in the late '80s/early'90s.


That should be late '70s/earlu'80's

--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail rpont (at) gmail (dot) com


  #12  
Old March 15th 19, 10:53 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 8,777
Default Missing Startup progs after WU

Terry Pinnell wrote:
Paul wrote:

Eric Stevens wrote:
On Fri, 15 Mar 2019 07:08:11 +1100, Monty wrote:

On Thu, 14 Mar 2019 15:40:12 +0000, Terry Pinnell
wrote:

After last night's WU to 1803 build 17134.648 several of my startup
programs are not loading.
That seems to be an old build. I updated two of my PCs a couple of
days ago and the build no is Version 1809 OS Build 17763.379
I've got one machine still on 1803. MS does not seem to want to offer
it 1809.

In the Settings Wheel : Update and Security, what does
the Windows Update History tab show ? Does it show an update
which is failed, and blocks other updates ? You can have
a "log jam", where WU is trying to get some older update
to install, and this prevents 1809 from being considered.

If you get the failed update (which is not followed by any
success entry with the same number), then you can go to
catalog.update.microsoft.com and get the MSU for that KB
via manual download. Double click it and install it.

There is usually sufficient logic (and wsusscn content) for
an MSU to figure out whether it's relevant or not. I've never
seen a case where trying to use an MSU caused a problem.

I found the "need to install 1809" was pretty aggressive
a couple days ago, and an install I didn't particularly want
updated, started to update on this machine. The cleanup
behavior is there, to "move on to the next thing".

If you've been messing around with "streams" and using the
Long Term business stream (whatever that's called today",
maybe you could break it that way. Also, in the past,
if you manually reverted the OS version (made the OS
loot C:\Windows.old and put things back), that also
functions as a "manual barrier" to upgrading. And running
a Repair Install by executing Setup.exe might be the simplest
way to move forward again.

By knowing things you've done to the OS along the way,
there may be some hint as to why.

I've also noticed, that a number of items referenced by
people on the web, concerning the Registry, and ways to
control this behavior, don't actually work. And a ton of
stuff that worked at one time, is just left there as
a "grave yard" of registry entries. Even if you did find
some registry entries that didn't match what it told
you to do on the web, it could be the OS isn't even paying
attention to those now. I used to look at those, when the
Insider Edition threw a wobbly, and fiddling that stuff as
instructed, didn't do a thing. The Insider is constantly doing
Upgrades, and is an excellent test vehicle for such.

Paul


Thanks Paul. I used my nightly backup of
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp
to replace those mysteriously lost entries and after a couple of reboots
things seem to be OK.

Why would WU not be updating some PCs to 1809 and should I be worried or
relieved that mine is one of them?

FWIW here's my recent Quality update history:

Quality Updates (21)

2019-03 Cumulative Update for Windows 10 Version 1803 for x64-based
Systems (KB4489868)
Successfully installed on 14/03/19
2019-03 Security Update for Adobe Flash Player for Windows 10 Version
1803 for x64—based Systems
Successfully installed on 14/03/19
2019-02 Update for Windows 10 Version 1803 for x64—based Systems
(KB4023057)
Successfully installed on 01/03/19
2019-02 Update for Windows 10 Version 1803 for x64—based Systems
(KB4023057)
Successfully installed on 15/02/19
2019-02 Cumulative Update for Windows 10 Version 1803 for x64—based
Systems (KB4487017)
Successfully installed on 13/02/19
2019-02 Security Update for Adobe Flash Player for Windows 10 Version
1803 for x64-based Systems
Successfully installed on 13/02/19
2018-10 Update for Windows 10 Version 1803 for x64-based Systems
(KB4100347)
Successfully installed on 06/02/19
2018-10 Update for Windows 10 Version 1803 for x64—based Systems
(KB4100347) (12)
Last failed install attempt on 04/02/19 - 0x80240034
2019-01 Update for Windows 10 Version 1803 for x64-based Systems
(KB4023057)
Successfully installed on 18/01/19
2018-11 Update for Windows 10 Version 1803 for x64-based Systems
(KB4023057) (2)
Last failed install attempt on 18/01/19 - 0x80070643
2019-01 Security Update for Adobe Flash Player for \Windows 10 Version
1803 for x64-based System
Successfully installed on 10/01/19
2019-01 Cumulative Update for Windows 10 Version 1803 for x64-based
Systems (KB4480966)
Successfully installed on 10/01/19

Terry, East Grinstead, UK


http://support.microsoft.com/help/4023057

"This update includes reliability improvements to Windows Update Service
components in consumer Windows 10, versions 1507, 1511, 1607, 1703, 1709,
and 1803. It may take steps to free up disk space on your device if you
do not have enough disk space to install Windows updates.

This update replaces the following updates:
2018-12 Update for Windows 10 Version 1507 for x86-based Systems (KB4023057)
2019-01 Update for Windows 10 Version 1507 for x86-based Systems (KB4023057)
2019-02 Update for Windows 10 Version 1507 for x86-based Systems (KB4023057)
"

Your KB4023057 failures have been overridden by the
2019-02 version success. We don't care about the old
versions once the new version installs. It's too bad the
versioning wasn't visible in the log entries, to make this
clearer for everybody, what is going on. If you didn't
read the KB, you might have no hint why there are so
many of them.

The space management features (as terrible as they are),
could help with tablet owners. I think MS notion of
space management is nuts, but that's just me (the idea
of "reserving space" for MS...).

Click check for updates, and see if anything is on offer.
When the system detects "you're a Seeker", it's supposed
to start things like the Upgrade.

I think I actually managed to get one 1809 install to happen,
without resorting to "Seeker" behavior, by clicking the Check
for Updates button. And it installed OK, and I had
turned off Delivery Service (DoSvc) and made it do
the install using BITS instead. I throttled the
BITS (via GPEDIT) so it couldn't open more than four
connections. The download behavior changes when you do that,
and it downloaded one 2.5GB file in a single shot,
instead of opening thousands of smaller packages
like it normally does on an OS Upgrade attempt.

I hope you have a backup in hand, before it starts.
While the installer has good behavior when dealing with
a good hard drive and good RAM, it's a lot harder for
an installer to successfully roll back an install attempt
on "sick" hardware. Making a backup give you an
option later, if there is trouble. Like if your SSD
seems to have the occasional problem needing CHKDSK.

Good luck :-)

Paul
  #13  
Old March 15th 19, 10:12 PM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 375
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 09:58:17 +0000 (GMT), "rp"
wrote:

On Fri, 15 Mar 2019 12:28:46 +1300, Eric Stevens wrote:

I've got one machine still on 1803. MS does not seem to want to offer
it 1809.


Soon Microsoft will bring back memories. I used to service ICL 1903
mainframes in the late '80s/early'90s.


What a birds nest made of spaghetti was the wiring in the back of the
cabinet of those things!
--

Regards,

Eric Stevens
  #14  
Old March 16th 19, 09:43 PM posted to alt.comp.os.windows-10
Eric Stevens
external usenet poster
 
Posts: 375
Default Missing Startup progs after WU

On Fri, 15 Mar 2019 06:37:32 -0400, Paul
wrote:

Eric Stevens wrote:

!803 is all it knows about. There is no evidence of problems with
updates. It hasn't been used much for several weeks and when I started
it up to read its history it gave me a list of three updates for 1803
which it is right now downloading and going to install. There was no
mention of 1809. I'll wait to see what the future holds.


You might be surprised to find it downloading 1809,
after the other update install.

In fact after downloading and installing three updates it is now fully
uptodate at 1803 version 17134.648.
--

Regards,

Eric Stevens
  #15  
Old March 16th 19, 10:46 PM posted to alt.comp.os.windows-10
nospam
external usenet poster
 
Posts: 2,827
Default Missing Startup progs after WU

In article , Eric Stevens
wrote:

!803 is all it knows about. There is no evidence of problems with
updates. It hasn't been used much for several weeks and when I started
it up to read its history it gave me a list of three updates for 1803
which it is right now downloading and going to install. There was no
mention of 1809. I'll wait to see what the future holds.


You might be surprised to find it downloading 1809,
after the other update install.

In fact after downloading and installing three updates it is now fully
uptodate at 1803 version 17134.648.


microsoft doesn't consider your hardware to be fully compatible with
1809.

at this point, you might as well wait for 19h1.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 12:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
Copyright ©2004-2019 PCbanter.
The comments are property of their posters.