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

I am having trouble uninstalling a KB.



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old October 12th 19, 12:13 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default I am having trouble uninstalling a KB.

Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines. Windows 10 will
not be getting any better any time soon. It is what it is.


Anyway, the vendor flagged two bad KB's:

Windows 10 version 1903 – KB4524147, KB4517389 ----
Windows 10 version 1809 – KB4524148, KB4519338
Windows 10 version 1803 – KB4524149
Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T

  #2  
Old October 12th 19, 04:19 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default I am having trouble uninstalling a KB.

T wrote:
Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines. Windows 10 will
not be getting any better any time soon. It is what it is.


Anyway, the vendor flagged two bad KB's:

Windows 10 version 1903 – KB4524147, KB4517389 ----
Windows 10 version 1809 – KB4524148, KB4519338
Windows 10 version 1803 – KB4524149
Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


https://www.bleepingcomputer.com/new...ates-manually/

wusa /uninstall /KB:4517389
wusa /uninstall /KB:4524147

At some point, whatever uninstall logic is going to fail,
if at some root level the update isn't actually there. The
Windows Update list may depend on the status of SoftwareUpdate
folder, and if you're an inveterate "nuker" of that folder,
perhaps a side effect is items missing from GUI listings.
There is a command here, but who knows whether it does
an actual scan for the thing, rather than relying on some
pre-boiled history.

https://www.tenforums.com/tutorials/...dows-10-a.html

wmic qfe list brief /format:table

Mine doesn't list 4524147.

You cannot destroy the history of the machine entirely.
Windows Update is always able to scan and "see" packages
which were put there. It's the GUI listing which may
be broken. The trick then, is to use the same API
that "wusa" uses.

One other thing to remember, is that some items installed
are marked "uninstallable", but I've seen a recipe for
changing the status bit for that after the fact. This
allows backing out separate "Servicing Stack" or "Black Hole"
patches. So rather than being "uninstallable",
they're "reversible, with work".

Just as there are Apps which claim to be "uninstallable",
but there is a bit in the database table for Apps, which
can change the "In-box" status of an application. However,
additional protection mechanisms may be present, and I don't
know the "next step" for those. For example, I removed "MSEdge",
but all that did was remove the icon and the rest of the
crap was still there, and still "ready to roll". This suggests
a multi-step recipe is needed. The Enterprise version ("stable"),
wasn't supposed to have MSEdge, because in the beginning it
was not mature enough - this suggests the OS can run without it.

*******

( https://www.tenforums.com/windows-10...oct-3-a-7.html )

There is a picture showing a Servicing Stack KB4520390.
KB4524147 patch to a patch
KB4520390 Servicing Stack Oct3

https://www.tenforums.com/attachment...3-a-cu-ssu.jpg

Maybe my SSD drive was late getting its updates and
that pair was pulled ? I don't know why that's not
showing up on mine. I'm at 18362.418, presumably because
of the Oct Patch Tuesday.

Paul
  #3  
Old October 12th 19, 07:56 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default I am having trouble uninstalling a KB.

On 10/11/19 8:19 PM, Paul wrote:
T wrote:
Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you
why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines.Â* Windows 10 will
not be getting any better any time soon.Â* It is what it is.


Anyway, the vendor flagged two bad KB's:

Â*Â*Â* Windows 10 version 1903 – KB4524147, KB4517389Â* ----
Â*Â*Â* Windows 10 version 1809 – KB4524148, KB4519338
Â*Â*Â* Windows 10 version 1803 – KB4524149
Â*Â*Â* Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


https://www.bleepingcomputer.com/new...ates-manually/


Â*Â* wusa /uninstall /KB:4517389
Â*Â* wusa /uninstall /KB:4524147

At some point, whatever uninstall logic is going to fail,
if at some root level the update isn't actually there. The
Windows Update list may depend on the status of SoftwareUpdate
folder, and if you're an inveterate "nuker" of that folder,
perhaps a side effect is items missing from GUI listings.
There is a command here, but who knows whether it does
an actual scan for the thing, rather than relying on some
pre-boiled history.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â* wmic qfe list brief /format:table

Mine doesn't list 4524147.

You cannot destroy the history of the machine entirely.
Windows Update is always able to scan and "see" packages
which were put there. It's the GUI listing which may
be broken. The trick then, is to use the same API
that "wusa" uses.

One other thing to remember, is that some items installed
are marked "uninstallable", but I've seen a recipe for
changing the status bit for that after the fact. This
allows backing out separate "Servicing Stack" or "Black Hole"
patches. So rather than being "uninstallable",
they're "reversible, with work".

Just as there are Apps which claim to be "uninstallable",
but there is a bit in the database table for Apps, which
can change the "In-box" status of an application. However,
additional protection mechanisms may be present, and I don't
know the "next step" for those. For example, I removed "MSEdge",
but all that did was remove the icon and the rest of the
crap was still there, and still "ready to roll". This suggests
a multi-step recipe is needed. The Enterprise version ("stable"),
wasn't supposed to have MSEdge, because in the beginning it
was not mature enough - this suggests the OS can run without it.

*******

(
https://www.tenforums.com/windows-10...oct-3-a-7.html
)

There is a picture showing a Servicing Stack KB4520390.
KB4524147 patch to a patch
KB4520390 Servicing Stack Oct3

https://www.tenforums.com/attachment...3-a-cu-ssu.jpg


Maybe my SSD drive was late getting its updates and
that pair was pulled ? I don't know why that's not
showing up on mine. I'm at 18362.418, presumably because
of the Oct Patch Tuesday.

Â*Â* Paul


Thank you!

If the offender does not show up in wmic, I think I will try
uninstalling it anyway

  #4  
Old October 12th 19, 08:33 AM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default I am having trouble uninstalling a KB.

T wrote:
On 10/11/19 8:19 PM, Paul wrote:
T wrote:
Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells
you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines. Windows 10 will
not be getting any better any time soon. It is what it is.


Anyway, the vendor flagged two bad KB's:

Windows 10 version 1903 – KB4524147, KB4517389 ----
Windows 10 version 1809 – KB4524148, KB4519338
Windows 10 version 1803 – KB4524149
Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


https://www.bleepingcomputer.com/new...ates-manually/


wusa /uninstall /KB:4517389
wusa /uninstall /KB:4524147

At some point, whatever uninstall logic is going to fail,
if at some root level the update isn't actually there. The
Windows Update list may depend on the status of SoftwareUpdate
folder, and if you're an inveterate "nuker" of that folder,
perhaps a side effect is items missing from GUI listings.
There is a command here, but who knows whether it does
an actual scan for the thing, rather than relying on some
pre-boiled history.

https://www.tenforums.com/tutorials/...dows-10-a.html


wmic qfe list brief /format:table

Mine doesn't list 4524147.

You cannot destroy the history of the machine entirely.
Windows Update is always able to scan and "see" packages
which were put there. It's the GUI listing which may
be broken. The trick then, is to use the same API
that "wusa" uses.

One other thing to remember, is that some items installed
are marked "uninstallable", but I've seen a recipe for
changing the status bit for that after the fact. This
allows backing out separate "Servicing Stack" or "Black Hole"
patches. So rather than being "uninstallable",
they're "reversible, with work".

Just as there are Apps which claim to be "uninstallable",
but there is a bit in the database table for Apps, which
can change the "In-box" status of an application. However,
additional protection mechanisms may be present, and I don't
know the "next step" for those. For example, I removed "MSEdge",
but all that did was remove the icon and the rest of the
crap was still there, and still "ready to roll". This suggests
a multi-step recipe is needed. The Enterprise version ("stable"),
wasn't supposed to have MSEdge, because in the beginning it
was not mature enough - this suggests the OS can run without it.

*******

(
https://www.tenforums.com/windows-10...oct-3-a-7.html
)

There is a picture showing a Servicing Stack KB4520390.
KB4524147 patch to a patch
KB4520390 Servicing Stack Oct3

https://www.tenforums.com/attachment...3-a-cu-ssu.jpg


Maybe my SSD drive was late getting its updates and
that pair was pulled ? I don't know why that's not
showing up on mine. I'm at 18362.418, presumably because
of the Oct Patch Tuesday.

Paul


Thank you!

If the offender does not show up in wmic, I think I will try
uninstalling it anyway


If Restore Points were set up, you could try to do it
that way.

In the past, people would tell you "remove the software first,
then use the Restore Point to correct any unrelated filetypes".
But since you don't seem to have the updates, maybe using
a Restore Point is the best you can do. (Take it back to
a date where the machine was working.)

The other thing you could try, is a "Windows Update Manager"
third party product, of which there are several, and one
of them no longer receives support.

But with Windows 10, we're really grasping at straws here.
As time passes, the OS will become "more and more unrepairable",
which is... bad for business.

Like, a couple years ago, I'd probably tell you to get the
invisible updates from catalog.update.microsoft.com and
try and jam them in. The servicing stack one goes first,
and you use the latest servicing stack (SSU) you can find.
When you do them manually like that, a lot of times you'll
get "this update is not for this machine" or similar. Which
basically means "there is an explanation for this, but
we're not telling you". As in some cases, if you installed

KB4520390 Servicing Stack Oct3

first, then the

KB4524147 patch to a patch

stops reporting it's "not for this machine", and it installs.

But that's hardly a way to do maintenance on a computer, in the
sense that only the simplest situations can be managed by
"guessing". And in this case, I'm having trouble understanding
what Microsoft was thinking with this "patch to a patch" idea.
WTF classification is this for a patch ? Presumably it
registers under its own KB number, and not the KB number
of the patch it's fixing ? Why wasn't the patch to a patch
merely "Original Patch, Version 2". Now is not the time to be
ruining the patch model I've got in my head. Any more
than a manufacturer should be painting pop cans red,
then deciding to arbitrarily put "Coke" or "Pepsi" in the
can, based on a coin flip. We need standards. We need
easy to understand labeling. So what is Microsoft
doing in this case ? Was it bad public relations (make
up a bull**** story), or what ? I don't get it.

Paul
  #5  
Old October 12th 19, 09:54 PM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default I am having trouble uninstalling a KB.

On 10/12/19 12:33 AM, Paul wrote:
T wrote:
On 10/11/19 8:19 PM, Paul wrote:
T wrote:
Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells
you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines.Â* Windows 10 will
not be getting any better any time soon.Â* It is what it is.


Anyway, the vendor flagged two bad KB's:

Â*Â*Â* Windows 10 version 1903 – KB4524147, KB4517389Â* ----
Â*Â*Â* Windows 10 version 1809 – KB4524148, KB4519338
Â*Â*Â* Windows 10 version 1803 – KB4524149
Â*Â*Â* Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


https://www.bleepingcomputer.com/new...ates-manually/


Â*Â*Â* wusa /uninstall /KB:4517389
Â*Â*Â* wusa /uninstall /KB:4524147

At some point, whatever uninstall logic is going to fail,
if at some root level the update isn't actually there. The
Windows Update list may depend on the status of SoftwareUpdate
folder, and if you're an inveterate "nuker" of that folder,
perhaps a side effect is items missing from GUI listings.
There is a command here, but who knows whether it does
an actual scan for the thing, rather than relying on some
pre-boiled history.

https://www.tenforums.com/tutorials/...dows-10-a.html


Â*Â*Â* wmic qfe list brief /format:table

Mine doesn't list 4524147.

You cannot destroy the history of the machine entirely.
Windows Update is always able to scan and "see" packages
which were put there. It's the GUI listing which may
be broken. The trick then, is to use the same API
that "wusa" uses.

One other thing to remember, is that some items installed
are marked "uninstallable", but I've seen a recipe for
changing the status bit for that after the fact. This
allows backing out separate "Servicing Stack" or "Black Hole"
patches. So rather than being "uninstallable",
they're "reversible, with work".

Just as there are Apps which claim to be "uninstallable",
but there is a bit in the database table for Apps, which
can change the "In-box" status of an application. However,
additional protection mechanisms may be present, and I don't
know the "next step" for those. For example, I removed "MSEdge",
but all that did was remove the icon and the rest of the
crap was still there, and still "ready to roll". This suggests
a multi-step recipe is needed. The Enterprise version ("stable"),
wasn't supposed to have MSEdge, because in the beginning it
was not mature enough - this suggests the OS can run without it.

*******

(
https://www.tenforums.com/windows-10...oct-3-a-7.html
)

There is a picture showing a Servicing Stack KB4520390.
KB4524147 patch to a patch
KB4520390 Servicing Stack Oct3

https://www.tenforums.com/attachment...3-a-cu-ssu.jpg


Maybe my SSD drive was late getting its updates and
that pair was pulled ? I don't know why that's not
showing up on mine. I'm at 18362.418, presumably because
of the Oct Patch Tuesday.

Â*Â*Â* Paul


Thank you!

If the offender does not show up in wmic, I think I will try
uninstalling it anyway


If Restore Points were set up, you could try to do it
that way.

In the past, people would tell you "remove the software first,
then use the Restore Point to correct any unrelated filetypes".
But since you don't seem to have the updates, maybe using
a Restore Point is the best you can do. (Take it back to
a date where the machine was working.)

The other thing you could try, is a "Windows Update Manager"
third party product, of which there are several, and one
of them no longer receives support.

But with Windows 10, we're really grasping at straws here.
As time passes, the OS will become "more and more unrepairable",
which is... bad for business.

Like, a couple years ago, I'd probably tell you to get the
invisible updates from catalog.update.microsoft.com and
try and jam them in. The servicing stack one goes first,
and you use the latest servicing stack (SSU) you can find.
When you do them manually like that, a lot of times you'll
get "this update is not for this machine" or similar. Which
basically means "there is an explanation for this, but
we're not telling you". As in some cases, if you installed

Â*Â* KB4520390 Servicing Stack Oct3

first, then the

Â*Â* KB4524147 patch to a patch

stops reporting it's "not for this machine", and it installs.

But that's hardly a way to do maintenance on a computer, in the
sense that only the simplest situations can be managed by
"guessing". And in this case, I'm having trouble understanding
what Microsoft was thinking with this "patch to a patch" idea.
WTF classification is this for a patch ? Presumably it
registers under its own KB number, and not the KB number
of the patch it's fixing ? Why wasn't the patch to a patch
merely "Original Patch, Version 2". Now is not the time to be
ruining the patch model I've got in my head. Any more
than a manufacturer should be painting pop cans red,
then deciding to arbitrarily put "Coke" or "Pepsi" in the
can, based on a coin flip. We need standards. We need
easy to understand labeling. So what is Microsoft
doing in this case ? Was it bad public relations (make
up a bull**** story), or what ? I don't get it.

Â*Â* Paul


Hi Paul,

I already approached him about freezing his machines
once I get them working again. They are point of sale
machines, but on my recommendation, he uses a stand
alone credit card reader, so PCI is placated. But
he looked at me glassy eyes and blankly when I told
him that if I freeze the machines, he has to buy
a good anti virus. (I will make sure and sell him
a three year license).

I would say, "What was M$ thinking?" firing their QC
department and relying on virtual machines and
telemetry, but M$ thinking has been beyond me for
years and years now.

This specialty software should port to Fedora (Linux),
but that will be a stretch as these customers need
their Quick Books, etc. to run on these machines,
so "hold you noses, things have to get better" is the
answer. Unfortunately, probably not in my lifetime.

Maybe we will start to see frozen OEM versions of
Windows Nein starting to appear in the future.

-T

  #6  
Old October 15th 19, 05:43 PM posted to alt.comp.os.windows-10
Walter Boyd
external usenet poster
 
Posts: 12
Default I am having trouble uninstalling a KB.

On 10/12/2019 2:33 AM, Paul wrote:





If Restore Points were set up, you could try to do it
that way.

Restore point worked for me... Just remember to pause updates for awhile
or it will download again the next time Windows checks for updates. -Walt
  #7  
Old October 15th 19, 12:30 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default I am having trouble uninstalling a KB.

On 10/11/19 4:13 PM, T wrote:
Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines.Â* Windows 10 will
not be getting any better any time soon.Â* It is what it is.


Anyway, the vendor flagged two bad KB's:

Â*Â*Â* Windows 10 version 1903 – KB4524147, KB4517389Â* ----
Â*Â*Â* Windows 10 version 1809 – KB4524148, KB4519338
Â*Â*Â* Windows 10 version 1803 – KB4524149
Â*Â*Â* Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


Followup:

Everyone is coming to work today and their printing issues are resolved.
Well except that I had to put the drive drives back to the right model
printer on one customer and reinstall a PDF driver on another. The
original customer on this post is not printing without any issues.

M$ must have rolled out the patch of the patch. Also, I don't see
KB:4524147 installed anywhere any more.

  #8  
Old October 15th 19, 02:49 AM posted to alt.comp.os.windows-10
n/a
external usenet poster
 
Posts: 75
Default I am having trouble uninstalling a KB.

"T" wrote in message ...

Hi All,

W10 Home 1903 x64

M$ did its thing again and two KB's broke a piece of my
customer's software.

This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

And well, this is expected when you fire your QC department
and rely on telemetry and virtual machines. Windows 10 will
not be getting any better any time soon. It is what it is.


Anyway, the vendor flagged two bad KB's:

Windows 10 version 1903 – KB4524147, KB4517389 ----
Windows 10 version 1809 – KB4524148, KB4519338
Windows 10 version 1803 – KB4524149
Windows 8.1 – KB4524156

Now these do show in installed updates:
https://ibb.co/zRtF4T5

Problem: when I go to "uninstall Updates" they don't exist:
https://ibb.co/5Yq9Py3

Notice that there are no scroll bars on the above.

How do I uninstall these two turkeys??????

Many thanks,
-T


--

T,

I'm assuming the vendor is Mitchell1 ?

Your problems may not be as over as you think. Make sure your client can
print Invoices, RO's and any other documents he uses within Mitchell. Long
story short, removing the updates did not resolve the issues on about 50% of
my clients systems. After Mitchell support got done with one system,
nothing worked. Restoring from a backup image prior to the Mitchell ver 8
update only created more problems and I ended up re-installing Win10 from
scratch back to 1809, re-installing Mitchell, upgrading to 1903 and
upgrading the Mitchell client then installing the latest Win10 updates (8
Oct) and then it worked.

I have other systems that did not have those two updates and they still
failed printing from within Mitchell. Had Mitchell support in on TV and
they verified that those updates were not installed and then scratched their
butts.

On another system, I uninstalled the two updates earlier today, rebooted and
still get the print error from within Mitchell that says there's a formula
error, missing ")". That error is from Crystal Reports. I can print from
other apps - just not Mitchell. I have a call in to the rep again but I
know what Mitchell support is going to say - "Reinstall Win10" their
standard response when they can't fix their own software.

As for what you see under View Update History versus what shows under
Uninstall Updates - that is a bit perplexing but the first shows what *was*
installed, the 2nd shows what *is* installed. It's sort of like figuring
out how many gpedit changes you need to go thru to get the update menus to
show/unhide/hide/include the Pause and Feature Update delay menu items. MS
has deprecated the Semi-Annual Channel and Targeted but it's still an
option and it works in 1903. I'm going with 60 day delays to hold 1909 at
bay for awhile since it's due to be released in Nov. I'll test on a
non-production systems first. Ver 1903 upgrades were as smooth as silk when
I updated. Had a couple of legacy systems that needed BIOS/UEFI updates and
graphics updates but everything was golden until these two updates....

Bob S.


  #9  
Old October 15th 19, 04:29 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default I am having trouble uninstalling a KB.

On 10/14/19 6:49 PM, n/a wrote:
T,

I'mÂ*assumingÂ*theÂ*vendorÂ*isÂ*Mitchell1Â*?

Your problems may not be as over as you think.Â* Make sure your client
can print Invoices, RO's and any other documents he uses within
Mitchell.Â* Long story short, removing the updates did not resolve the
issues on about 50% of my clients systems.Â* After Mitchell support got
done with one system, nothing worked. Restoring from a backup image
prior to the Mitchell ver 8 update only created more problems and I
ended up re-installing Win10 from scratch back to 1809, re-installing
Mitchell, upgrading to 1903 and upgrading the Mitchell client then
installing the latest Win10 updates (8 Oct)Â*andÂ*thenÂ*itÂ*worked.

I have other systems that did not have those two updates and they still
failed printing from within Mitchell.Â* Had Mitchell support in on TV and
they verified that those updates were not installed and then scratched
their butts.

On another system, I uninstalled the two updates earlier today, rebooted
and still get the print error from within Mitchell that says there's a
formula error, missing ")".Â* That error is from Crystal Reports.Â* I can
print from other apps - just not Mitchell.Â* I have a call in to the rep
again but I know what Mitchell support is going to say - "Reinstall
Win10" their standardÂ*responseÂ*whenÂ*theyÂ*can'tÂ*fixÂ*their *ownÂ*software.

As for what you see under View Update History versus what shows under
Uninstall Updates - that is a bit perplexing but the first shows what
*was* installed, the 2nd shows what *is* installed.Â* It's sort of like
figuring out how many gpedit changes you need to go thru to get the
update menus to show/unhide/hide/include the Pause and Feature Update
delay menu items. MS has deprecated theÂ* Semi-Annual Channel and
Targeted but it's still an option and it works in 1903.Â* I'm going with
60 day delays to hold 1909 at bay for awhile since it's due to be
released in Nov.Â* I'll test on a non-production systems first.Â* Ver 1903
upgrades were as smooth as silk when I updated.Â* Had a couple of legacy
systems that needed BIOS/UEFI updates and
graphicsÂ*updatesÂ*butÂ*everythingÂ*wasÂ*goldenÂ*u ntilÂ*theseÂ*twoÂ*updates....

BobÂ*S.


Hi Bob,

Yes, This was Mitchell1. Today, they can print without Mitchell1
crashing. But it was only the owner using it
today. Tomorrow both his staff members come in and I don't think I want
to know. Fortunately one of the three Mitchell1
computers is on Windows 7.

I am thinking, get it working and lock the turkeys down.
I proposed this to the owner, but told him first he has
to get a good anti virus.

On another client, it switched the print drivers on their main printer
to M$ Raster print driver. It was pretty easy to switch back to HP 477
in properties, advanced. It also deleted a PDF printer required by the
software. This was Mitchel without the "1" -- two different pieces of
software.
(Yes, I now have notes all over the place as to the
difference.)

An another client with two computers on Site Link had
it corrupt the spooler and all their print drivers. That
took a force of nature to fix, but I did.

Thank you for the wonderful write up!
-T

  #10  
Old October 16th 19, 01:48 AM posted to alt.comp.os.windows-10
Kenny McCormack
external usenet poster
 
Posts: 160
Default What happened to the YouTube vid (Why Win10 has so many bugs) (Was: I am having trouble uninstalling a KB.)

In article , T wrote:
....
This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA


Note: This video seems to have been pulled. Wonder why???

It was working a few days ago (and I was able to view it), but is gone now.

Does anyone have a private copy they'd be willing to share?

--
In the corner of the room on the ceiling is a large vampire bat who
is obviously deranged and holding his nose.
  #11  
Old October 16th 19, 02:40 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default What happened to the YouTube vid (Why Win10 has so many bugs)

On 10/15/19 5:48 PM, Kenny McCormack wrote:
In article , T wrote:
...
This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA


Note: This video seems to have been pulled. Wonder why???

It was working a few days ago (and I was able to view it), but is gone now.

Does anyone have a private copy they'd be willing to share?


It is still working here. Try it again.
  #12  
Old October 16th 19, 02:49 AM posted to alt.comp.os.windows-10
Char Jackson
external usenet poster
 
Posts: 10,449
Default What happened to the YouTube vid (Why Win10 has so many bugs) (Was: I am having trouble uninstalling a KB.)

On Wed, 16 Oct 2019 00:48:42 -0000 (UTC), (Kenny
McCormack) wrote:

In article , T wrote:
...
This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA

Note: This video seems to have been pulled. Wonder why???

It was working a few days ago (and I was able to view it), but is gone now.

Does anyone have a private copy they'd be willing to share?


The link works fine for me, but I can't say that I learned anything from
watching it.

  #13  
Old October 16th 19, 02:53 AM posted to alt.comp.os.windows-10
nospam
external usenet poster
 
Posts: 4,718
Default What happened to the YouTube vid (Why Win10 has so many bugs) (Was: I am having trouble uninstalling a KB.)

In article , Kenny McCormack
wrote:

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA


Note: This video seems to have been pulled. Wonder why???


no it hasn't.

It was working a few days ago (and I was able to view it), but is gone now.


it's still there.

Does anyone have a private copy they'd be willing to share?


no need.
  #14  
Old October 16th 19, 04:12 AM posted to alt.comp.os.windows-10
T
external usenet poster
 
Posts: 4,600
Default What happened to the YouTube vid (Why Win10 has so many bugs)

On 10/15/19 5:48 PM, Kenny McCormack wrote:
In article , T wrote:
...
This issue will continue to be a problem with M$ Updates.
For an explanation of why, see

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA


Note: This video seems to have been pulled. Wonder why???

It was working a few days ago (and I was able to view it), but is gone now.

Does anyone have a private copy they'd be willing to share?


I downloaded it, but it is 3 GB. If the link does not
start working, do you have somewhere to upload it?
  #15  
Old October 16th 19, 04:17 AM posted to alt.comp.os.windows-10
nospam
external usenet poster
 
Posts: 4,718
Default What happened to the YouTube vid (Why Win10 has so many bugs) (Was: I am having trouble uninstalling a KB.)

In article , wrote:

Why does Microsoft Windows 10 have so many bugs? Ex-Employee tells you why!
https://www.youtube.com/watch?v=S9kn8_oztsA


Note: This video seems to have been pulled. Wonder why???

It was working a few days ago (and I was able to view it), but is gone now.

Does anyone have a private copy they'd be willing to share?


I downloaded it, but it is 3 GB. If the link does not
start working, do you have somewhere to upload it?


720p, the largest size available, is 149.3 megabytes.
 




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 09:52 AM.


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