Installing win10 over W\in 10

"T" wrote in message ...
On 2020-06-26 03:54, SC Tom wrote:


Find your laptop cord, fire it up, connect to the internet, and go he
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html
I've used this method on a couple of different PCs; one using a DVD made
from the ISO file, and another using the Media Creation Tool. All methods
assume that you can boot up Windows as an admin.

It's not a quick solution- it takes quite some time to complete. But to
me it was worth it- saved me from re-installing beau coup plenty programs
:-)

If you have a working back-up and the "upgrade" fails, you can always
restore it back to where you were if the PC doesn't boot. Good idea to
have the backups any how, IYKWIM.


Hi Tom,

I looked over the link. I have done this several times
for people with jammed build upgrades. But never to repair
the current build.

What I am wondering is, on the following screen, will
if still do an in place repair if the build it the same?

https://www.tenforums.com/attachment...ion_tool-2.png

Also, if the above does work for an in place repair
of the same build, what benefit does it give over?

1. sfc /scannow
2. dism /online /cleanup-image /checkhealth

Which I also frequently do. Sometimes I do it
from the ISO's command prompt.

-T

I'm not sure if the "it" in "build it the same" is meant to be "is" or
"isn't", but to quote the 1st link; "The installation media (ex: ISO or USB)
must be the same edition and same or newer build as your currently installed
Windows 10. If it's not, then the repair install will fail."

The advantage over SFC is that it will repair pretty much everything without
having to trying to fix those items that SFC didn't/couldn't fix.
I wrote a little batch file to show me any errors that SFC may run into and
didn't fix, so at least I don't have to scan through that massive log to
find them.

I haven't used the DISM command, so I can't answer that one. Maybe on my
next problem I'll try that ;-)
--

SC Tom

In alt.comp.os.windows-10, on Fri, 26 Jun 2020 13:15:19 -0700, T
wrote:

On 2020-06-26 03:18, mechanic wrote:
Readded so I can reply in one place:
Tried the Dell Supportassist system?

https://www.dell.com/support/content.../supportassist

I didnt' know about that but I'm looking at it right now.

-obviously requires a (minimally) working PC first!

For in-place reinstall of Windows I use the two commands:

1. sfc /scannow

I'd done this but I did it again.

2. dism /online /cleanup-image /checkhealth

I did this too when I first read your post, Mechanic. The print was
very small and dim and I had to use a magnifying glass, but I thought it
said everything was okay.

Now I'm in Safe mode and it might be coincidence (since even in regular
mode a few days ago I once went three days without a crash) but I
haven't crashed for 24 hours, and I tried the same instruction again and
got

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.329

Error: 87

The cleanup-image option is unknown.
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
-------------

I use the /Restorehealth switch

DISM.exe /Online /Cleanup-image /Restorehealth

I just tried this and I got the same error 87 and the same message, but
I suspect that is because I'm in Safe mode. I will try again in regular
mode, but sometimes I only have 30 seconds or less.

I was planning on starting the next time in Diagnostic Startup mode, but
after Hibernating last night, I see that I'm set for Selective Startup
with the first two of three boxes checked. Is that the mode I'm in
now? Or the one it plans for me next time? :-) Very few of the
services are running, but most of the startup programs.

I disabled a few of each that I know I don't need, but I don't know if
they will still be disableed after I reboot.

In alt.comp.os.windows-10, on Fri, 26 Jun 2020 06:54:35 -0400, "SC Tom"
wrote:



"Micky" wrote in message
.. .
On Thu, 25 Jun 2020 21:46:42 -0400, Paul
wrote:

Micky wrote:
I tried to install win10 over win10, and I was able to get to 60% but
ten seconds afterr I moved the mouse so that the screen lit up again,
it crashed.

And even if it got to 99%, it says it's going to have to start
windows several times, and t here's n o way it coud boot even twice
in a row without crashing 30 seconds later for one of those times.

So I dug out the XP laptop to get back on line, and soon after that I
had a new plan:

Instead of installing win10 over the win10 IN the computer, I'll take
the drve out, put it in a dock, plug the dock into the XP laptop, and
run the win10 install program I made using the Media Creator.

That's one of the intended uses, isn't it? And since the XP laptop
never crashes, and iiuc it won't have to restart anything, since i'm
updating what is not the operating system in use, so it will go faster
too.

Will this work?

Will it work better with my win7 laptop?
(I'm still looking for the cord for that but I t hink I know where
it is.)

So I think the summary of what you're saying is, you have
a pile of electronic hardware, but it's not a computer
any more. Because it does not reliably compute.

How will "sneaking up on it" help ? What will be
the eventual outcome ? At a critical moment, it'll
throw you under the bus.

I don't have any critical moments. If the computer fails, I'll dig
out the laptop.

It would be like owning an automobile, with non-working
brakes (no fluid, lines cut), punching a hole in the

No, because a car without brakes is dangerous.

floor boards, so you can stick your feet down to stop.
Is it a car any more ? Or a pile of parts for sale ?

You need some sort of test utilities to narrow down
what hardware is defective. Which is not necessarily easy.

But I don't have any of those utilities and it's not easy.

Some brands of OEM computer, come with diagnostics on the

This was a Dell Optiplex 755 or 775 or something but it wasn't win10
originally. Any debugging it has came with a Win10 DVD that the
computer shop used to upgrade this for resale. G526mg1

hard drive. But not many of those are noteworthy. I liked
the diagnostics provided on Sun Sparc, because they weren't
just "sham diagnostics". The diagnostics were designed to
detect trouble.

I've purchased diagnostics before, that turned out
to be sham routines, and just intended to suck money
out of your wallet. The topic is very much "live and learn".

So that's no solution.

Anyhow, this is what I want to do. I posted to find out if whether MS
makes it impossible to do, and for hints on how to do it, like whether
it's worth waiting until I find the Win7 laptop cord

Paul


Find your laptop cord,

Found it! It was hidden well, still in my suitcase in a black plastic
bag.

fire it up, connect to the internet, and go he
https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

I've used this method on a couple of different PCs; one using a DVD made
from the ISO file, and another using the Media Creation Tool. All methods

Okay, I created a version on a flash drive using the Media Creation
tool. And I'm ready to try it, but....

assume that you can boot up Windows as an admin.

It's not a quick solution- it takes quite some time to complete. But to me

IIRC there are 2 or 3 reboots during a Windows install, but IIUC the
windows overlay isn't actually done until the last step, which means it
will run fine when run from the USB flashdrive, but when it's time to
reboot, it will boot into my current** OS and will crash soon
thereafter, is that right? Or has most of the overlaying been done by
that time?

If the answser is bad, can I use msconfig to set the next reboot to be
safe mode so it won't crash. Will it still be able to install? Is
everything needed to install in the USB drive so that Windows Safe Mode
is good enough?

**I'ld admit this sounds like a bad design, unreaonsable, but it's what
I've though happens. Wait... if the USB drive is still plugged in will
it reboot from the USB drive? Do I need to set the boot order to put
USB first. Currently when I star I press F12 and pick the USB drive,
but I might not be in the room during the reboot.

it was worth it- saved me from re-installing beau coup plenty programs :-)

Right. Exactly what I want to avoid.

If you have a working back-up

You know, I was going to save the previous clone, and I didn't. I
overlaid it because the location was already set up. Now I regret that,
because I did swap HDDs and the clone, created by Macrium Reflect,
started right up, looked and worked just like the original and crashed 2
times just like the original.

and the "upgrade" fails, you can always
restore it back to where you were if the PC doesn't boot. Good idea to have
the backups any how, IYKWIM.

I do have another copy of my data, but I hate all the work reinserting
that will require. I'd much rather do this sort of work which is
challenging and not clerical.

In alt.comp.os.windows-10, on Sat, 27 Jun 2020 08:29:05 -0400, "SC Tom"
wrote:


1. sfc /scannow

I tried this a 3rd time, still in Safe mode and got:

Windows Resource Protection could not start the repair service.

So it's clear that Safe mode prevents this and DISM from running.

But I'll run them again in regular mode.

micky wrote:
In alt.comp.os.windows-10, on Sat, 27 Jun 2020 08:29:05 -0400, "SC Tom"
wrote:

1. sfc /scannow

I tried this a 3rd time, still in Safe mode and got:

Windows Resource Protection could not start the repair service.

So it's clear that Safe mode prevents this and DISM from running.

But I'll run them again in regular mode.


You can boot a Windows 10 installer DVD and use the
Command Prompt there.

There are "offline" versions of SFC and DISM command
parameters that are supposed to work there. When doing
it offline, you have to tell it the drive letter of the
partition needing a scan.

But with your Safe Mode success, that hints at a driver
level problem. Maybe something about the AV.

Paul

In alt.comp.os.windows-10, on Thu, 25 Jun 2020 20:31:03 -0700, T
wrote:

On 2020-06-25 20:10, Micky wrote:
On Thu, 25 Jun 2020 20:00:35 -0700, T wrote:

On 2020-06-25 19:44, Micky wrote:
On Thu, 25 Jun 2020 18:33:54 -0700, T wrote:

On 2020-06-25 18:23, Micky wrote:
I tried to install win10 over win10, and I was able to get to 60% but
ten seconds afterr I moved the mouse so that the screen lit up again,
it crashed.

And even if it got to 99%, it says it's going to have to start
windows several times, and t here's n o way it coud boot even twice
in a row without crashing 30 seconds later for one of those times.

So I dug out the XP laptop to get back on line, and soon after that I
had a new plan:

Instead of installing win10 over the win10 IN the computer, I'll take
the drve out, put it in a dock, plug the dock into the XP laptop, and
run the win10 install program I made using the Media Creator.

That's one of the intended uses, isn't it? And since the XP laptop
never crashes, and iiuc it won't have to restart anything, since i'm
updating what is not the operating system in use, so it will go faster
too.

Will this work?

Will it work better with my win7 laptop?
(I'm still looking for the cord for that but I t hink I know where
it is.)


Are you trying to do a wipe and reinstall?

Sorry, in my mind I was conintuing a thread.

dI don't want to wipe anything, certainly not my installed program,
non-windows programs or my data or settings or anything else, but
there may be a windows file that is fowled up. In another thread,
someone whose name I can't remember right now said that he fixed a
problem similar to mine, BSODs with various reasons, by installing
Windows on top of windows.

So that's what I want to do.

When I tried to do it from the win10 computer itself, it crashed too
often to finish, but that won't be a problem if the windows drive is
in a dock. After t he install is complete, I'll put it back in the
computer.

This is an instended use of the windows10 installation file,
right??????

Maybe not so often win on top of window, but maybe more often onto a
blank drive, but if it is meant to do that, it will do this.


in place re-installs went out with XP.

The best I can find is to open an administrator's cmd
and do a

sfc /scannow

If you are not on build (WinVer.exe) 2004, you can do
an in place upgrade with

https://www.microsoft.com/en-us/soft...d/windows10ISO

HTH


Thanks and thanks for the prompt reply. I've done SFC and I thought
the ver 2004 upgrade might do it, but it didn't.

As to in-place reinstalls going out with XP, I found MS pages
discussing how to do it with w10. Unfortunately those links are in the
problem computer so I can't look at them again right now, and I dont'
want to take the time to hunt the web for them, but... They had about
3 major options and one of them had 3 suboptions, one of which was
in-place and another was iirc "another computer" I don't know how
you can upate another computer without taking the HDD out. The days
of running a cable from the sereis port to the other series port are
gone, and I don't think you could do it with a USB cable without some
additional software.

So I'll try it and whether it works or not, I'll be back in the bad
computer eventually and I'll look for those pages, see what the exact
words were, and if need be google them f or an explanation.

And I plan to post back what I learn.


Hi Micky,

Not to ask too stupid a question, but what is not
working right? Maybe the guys here can help you
fix it.

I had a couple earlier threads about my BSOD's with various causes
listed, at least 6 or 7 different reasons given.

Also, do you have a spare hard drive you can replace it
with and make sure it install W10 okay. Maybe something
is wrong with your hardware

That's a point. Yes, I have a spare HDD, but I'm 99% sure it will run
fine with just Windows 10 installed. I think the problem lies with one
of the programs or files, among all the others I've installed and want
to keep using.

I ran Memtest88 for 9 hours with no errors found. It's been running***
for 16 hours in Safe Mode. If it were the hardware, could it do that?
I looked at the mobo caps and one might be a little high in the middle,
or not. I'll look again with a straight edge. That leaves the BIOS,
the CPU, and other chips on board. Do they fail?

***I can do all sorts of things in Safe Mode. I can receive, compose,
and send in Usenet, and in Email I can compose, send, and receive email
(although Eudora will fetch mail and store it in the right mailbox but I
can't open it to read it! (I can read my email on the laptop or the
phone until I get this fixed.) I can use Firefox except I can't play
videos. (I suppose if I coud figure out and find the right service or
startup program and I enabled or started it, I could do that too.)

Speccy doesn't know how hot my CPU is.

-T

In alt.comp.os.windows-10, on Sat, 27 Jun 2020 13:24:45 -0400, Paul
wrote:



You can boot a Windows 10 installer DVD and use the
Command Prompt there.

I dont' think I have one of those. Unless I can use the Flash drive
made by Media Creator. if not, I can run it again to make a DVD.
Should I do that? I'm glad to say my laptop has a DVD reader/writer.

There are "offline" versions of SFC and DISM command
parameters that are supposed to work there. When doing

So I just have to take the HDD out, put it in my dock, and run the
programs from the laptop??

it offline, you have to tell it the drive letter of the
partition needing a scan.

A good reminder.

But with your Safe Mode success, that hints at a driver
level problem. Maybe something about the AV.

Of the webpages I read, one said to try to find a better driver for
everything listed in Device Manager, but another page by someone else
just said to look for yellow triangles. Which do you guys think is the
right answer??

micky wrote:
In alt.comp.os.windows-10, on Sat, 27 Jun 2020 13:24:45 -0400, Paul
wrote:


You can boot a Windows 10 installer DVD and use the
Command Prompt there.

I dont' think I have one of those. Unless I can use the Flash drive
made by Media Creator. if not, I can run it again to make a DVD.
Should I do that? I'm glad to say my laptop has a DVD reader/writer.

There are "offline" versions of SFC and DISM command
parameters that are supposed to work there. When doing

So I just have to take the HDD out, put it in my dock, and run the
programs from the laptop??

it offline, you have to tell it the drive letter of the
partition needing a scan.

A good reminder.

But with your Safe Mode success, that hints at a driver
level problem. Maybe something about the AV.

Of the webpages I read, one said to try to find a better driver for
everything listed in Device Manager, but another page by someone else
just said to look for yellow triangles. Which do you guys think is the
right answer??

Your USB stick Windows 10 installer, will also offer Command Prompt,
somewhere in the troubleshooting section.

You have to find the syntax for the offline versions of the commands.

I don't know if it's a "better driver" exactly, but something
is amiss in Ring0, and drivers with bad memory usage characteristics
are one reason for bad things to happen. It's really beyond my
pay scale to debug these things. I tried Driver Verifier once,
but as soon as I turned it on, the problem went away, so
it's "pretty hard to measure something that goes away".

*******

# While in the OS

Dism /Online /Cleanup-Image /ScanHealth

# While booted from a USB stick, Command Prompt...

Dism /Image:C:\ /Cleanup-Image /ScanHealth
Dism /Image:C:\ /Cleanup-Image /RestoreHealth

*******

SFC is a troublemaker, and getting the thing pointed
at the right stuff is a pain.

http://winaero.com/blog/how-to-run-t...does-not-boot/

"sfc /scannow /offbootdir=C:\ /offwindir=D:\Windows

Note that offbootdir contains the letter of your "System Reserved"
partition and offwindir is the volume on which your broken,
unbootable Windows 10 is located.
"

Paul

In alt.comp.os.windows-10, on Sat, 27 Jun 2020 14:55:26 -0400, Paul
wrote:

micky wrote:
In alt.comp.os.windows-10, on Sat, 27 Jun 2020 13:24:45 -0400, Paul
wrote:


You can boot a Windows 10 installer DVD and use the
Command Prompt there.

I dont' think I have one of those. Unless I can use the Flash drive
made by Media Creator. if not, I can run it again to make a DVD.
Should I do that? I'm glad to say my laptop has a DVD reader/writer.

There are "offline" versions of SFC and DISM command

IIUC in order to use DISM to fix Windows, I absolutely need a /Source
that points to a good win10. It can't just figure it out by itself, like
SFC seems to be able to do.

I believe I fouled up my only clone, that I made after the BSODs had
started. It can't use whatever is on the Flashdrive, can it?

So I either have to borrow a PC with a harddrive I can remove and put in
a dock,

or I have to take one of my blank HDD's and put it in one of my second
hand PC's and install 10 onto it from the media creator version. And
then I can remove that HDD and put it into the dock.

Well maybe not.
https://docs.microsoft.com/en-us/win...-repair-source
says:

Choose a Repair Source

You can use Windows Update to provide the files that are required to
restore a Windows feature or *repair a corrupted operating system*. You
can also configure Group Policy to gather the required files from a
network location. Multiple source locations can be specified in the
Group Policy.

Use Windows Update to restore optional features and repair Windows
images

Windows Update will be used by default if it is allowed by the
policy settings on the computer. [I have no idea what the policy
settings are, but I'll find out.]

If you want to use Windows Update as a primary or backup source for
files that are used to restore optional features or repair Windows
images, you should make sure that your firewall is configured to allow
access to Windows Update. [Of course]


Use a network location to restore optional features and repair Windows
images

You can use a mounted Windows image from a WIM file as a source to
restore optional features and repair a corrupted operating system. For
example, c:\test\mount\Windows. For more information about capturing a
Windows image as a WIM file, see Capture Images of Hard Disk Partitions
Using DISM.

You can use a running Windows installation as a source to restore
optional features by sharing the c:\Windows folder on your network.

You can use a Windows side-by-side folder from a network share or
from a removable media, such as the Windows DVD, as the source of the
files. For example, z:\sources\SxS.
[I should consider this, I guess. ]

You can use a Windows image (.wim) file on a network share as a
source to restore optional features. You must specify the index of the
Windows image in the .wim file that you want to use and you must use a
Wim: prefix in the path to identify this file format. For example, to
specify index 3 in a file named contoso.wim, type:
Wim:\\network\images\contoso.wim:3.


parameters that are supposed to work there. When doing

So I just have to take the HDD out, put it in my dock, and run the
programs from the laptop??

it offline, you have to tell it the drive letter of the
partition needing a scan.

A good reminder.

But with your Safe Mode success, that hints at a driver
level problem. Maybe something about the AV.

Of the webpages I read, one said to try to find a better driver for
everything listed in Device Manager, but another page by someone else
just said to look for yellow triangles. Which do you guys think is the
right answer??

Your USB stick Windows 10 installer, will also offer Command Prompt,
somewhere in the troubleshooting section.

You have to find the syntax for the offline versions of the commands.

I don't know if it's a "better driver" exactly, but something
is amiss in Ring0, and drivers with bad memory usage characteristics
are one reason for bad things to happen. It's really beyond my
pay scale to debug these things. I tried Driver Verifier once,
but as soon as I turned it on, the problem went away, so
it's "pretty hard to measure something that goes away".

*******

# While in the OS

Dism /Online /Cleanup-Image /ScanHealth

# While booted from a USB stick, Command Prompt...

Dism /Image:C:\ /Cleanup-Image /ScanHealth
Dism /Image:C:\ /Cleanup-Image /RestoreHealth

*******

SFC is a troublemaker, and getting the thing pointed
at the right stuff is a pain.

http://winaero.com/blog/how-to-run-t...does-not-boot/

"sfc /scannow /offbootdir=C:\ /offwindir=D:\Windows

Note that offbootdir contains the letter of your "System Reserved"
partition and offwindir is the volume on which your broken,
unbootable Windows 10 is located.
"

Paul

On 2020-06-27 10:45, micky wrote:

BSOD: Did you install "Who Crashed" and look at the report?
(Let me know if you need the link.)

That's a point. Yes, I have a spare HDD, but I'm 99% sure it will run
fine with just Windows 10 installed. I think the problem lies with one
of the programs or files, among all the others I've installed and want
to keep using.

I would try it anyway.

And easier thing to do is to download and cut a Live USB
of Fedora. Boot off that and surf the internet and such
to see if yo have any issues. It is a good way to tell
if you have a hardware issue. You can also install gsmartcontrol in the
Live USB and test your hard drive
(Let me know if you need links.)



I ran Memtest88 for 9 hours with no errors found.

If you are running non-ecc hardware, those memory tests are
next to worthless. The only way I have found that gets
bad memory all the time is to sway them out with known
good memory. (I do not sell customer computers with out
ecc chipsets and ecc memory as I consider it to be unethical.)

It's been running***
for 16 hours in Safe Mode. If it were the hardware, could it do that?

A YUGE "perhaps". Most probably not. Safe mode does not
use the direct chipset drivers, but instead uses the generic
drivers.

Safe mode pretty much eliminates your memory

I looked at the mobo caps and one might be a little high in the middle,
or not. I'll look again with a straight edge.

When the caps go out, you typically brick.

That leaves the BIOS,
the CPU, and other chips on board. Do they fail?

Yes, not very often though. 99% of the time it is
Windows causing the issue (software). When I come
across an actual hardware problem, I am usually
chasing the wrong rabbit down the wrong hole and
am surprised when I realize it is actually hardware.

But this shows up like a soar thumb with a Live USB.

Just an aside. I can only make it through only
about one build upgrade. When I wipe and reinstall
and do my "Windows de-fang" routine, Windows 10
settings down. This is why I wanted you to try a
spare hard drive.

On 2020-06-27 11:55, Paul wrote:
SFCÂ*isÂ*aÂ*troublemaker,Â*andÂ*gettingÂ*theÂ*thin gÂ*pointed
atÂ*theÂ*rightÂ*stuffÂ*isÂ*aÂ*pain.

Always trips me up too. I even have it in
my documents and forget it.

On 2020-06-27 05:29, SC Tom wrote:
I'm not sure if the "it" in "build it the same" is meant to be "is" or
"isn't", but to quote the 1st link; "The installation media (ex: ISO or
USB) must be the same edition and same or newer build as your currently
installed WindowsÂ*10.Â*IfÂ*it'sÂ*not,Â*thenÂ*theÂ*repairÂ*i nstallÂ*willÂ*fail."

Hi Tom,

That was my concern. I have used the technique to
"upgrade" the build, but never to reinstall the
current build. And since these How-To's have a lot
of goofs in them, I wanted to verify with you if
you have actually got it to work with the "current"
build.

-T

T wrote:
On 2020-06-27 05:29, SC Tom wrote:
I'm not sure if the "it" in "build it the same" is meant to be "is" or
"isn't", but to quote the 1st link; "The installation media (ex: ISO
or USB) must be the same edition and same or newer build as your
currently installed
Windows 10. If it's not, then the repair install will fail."

Hi Tom,

That was my concern. I have used the technique to
"upgrade" the build, but never to reinstall the
current build. And since these How-To's have a lot
of goofs in them, I wanted to verify with you if
you have actually got it to work with the "current"
build.

-T


Yes, it works with a Current build. I've done it.

That's a Repair Install of a running OS. 1909 to 1909.

If you take a 1909, and run Setup.exe off the 2004 DVD,
that's an Upgrade Install.

Going *backwards*, is an unknown. The Setup.exe
might even stop dead in its tracks if you go backwards...

Paul

On 2020-06-27 13:43, Paul wrote:
T wrote:
On 2020-06-27 05:29, SC Tom wrote:
I'm not sure if the "it" in "build it the same" is meant to be "is"
or "isn't", but to quote the 1st link; "The installation media (ex:
ISO or USB) must be the same edition and same or newer build as your
currently installed Windows 10. If it's not, then the repair install
will fail."

Hi Tom,

That was my concern.Â* I have used the technique to
"upgrade" the build, but never to reinstall the
current build.Â* And since these How-To's have a lot
of goofs in them, I wanted to verify with you if
you have actually got it to work with the "current"
build.

-T


Yes, it works with a Current build. I've done it.

That's a Repair Install of a running OS. 1909 to 1909.

If you take a 1909, and run Setup.exe off the 2004 DVD,
that's an Upgrade Install.

Going *backwards*, is an unknown. The Setup.exe
might even stop dead in its tracks if you go backwards...

Â*Â* Paul

Awesome! Thank you!

In alt.comp.os.windows-10, on Sat, 27 Jun 2020 14:55:26 -0400, Paul
wrote:

micky wrote:
In alt.comp.os.windows-10, on Sat, 27 Jun 2020 13:24:45 -0400, Paul
wrote:


You can boot a Windows 10 installer DVD and use the
Command Prompt there.

I dont' think I have one of those. Unless I can use the Flash drive
made by Media Creator. if not, I can run it again to make a DVD.
Should I do that? I'm glad to say my laptop has a DVD reader/writer.

There are "offline" versions of SFC and DISM command
parameters that are supposed to work there. When doing

So I just have to take the HDD out, put it in my dock, and run the
programs from the laptop??

it offline, you have to tell it the drive letter of the
partition needing a scan.

A good reminder.

But with your Safe Mode success, that hints at a driver
level problem. Maybe something about the AV.

Of the webpages I read, one said to try to find a better driver for
everything listed in Device Manager, but another page by someone else
just said to look for yellow triangles. Which do you guys think is the
right answer??

Your USB stick Windows 10 installer, will also offer Command Prompt,
somewhere in the troubleshooting section.

You have to find the syntax for the offline versions of the commands.

I don't know if it's a "better driver" exactly, but something
is amiss in Ring0, and drivers with bad memory usage characteristics
are one reason for bad things to happen. It's really beyond my
pay scale to debug these things. I tried Driver Verifier once,
but as soon as I turned it on, the problem went away, so
it's "pretty hard to measure something that goes away".

*******


I started this session normally and it hasn't crashed yet, even though I
know nothing has been fixed. I have TCC/Le started, Agent 1.93, Firefox
and xplorer2, and notpad++. and msconfig. I think that's been enough
to crash it in the past.

I also ran Primenn, but only for 2 hours. No apparent errors.

I think I'll wait unti the next crasnh and then try to Reinstall win10

# While in the OS

Dism /Online /Cleanup-Image /ScanHealth

# While booted from a USB stick, Command Prompt...

Dism /Image:C:\ /Cleanup-Image /ScanHealth
Dism /Image:C:\ /Cleanup-Image /RestoreHealth
..


I ran the two suggestions above in sequence and got:

Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.329

No component store corruption detected.
The operation completed successfully.

[Only took a couple minutes]

[C:\Programs\TCCLE14]dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.329

Image Version: 10.0.19041.329

[============= 22.7% ]

Restore Operation Completed Successfully


Took about 30 minutes. (I have the time in the log.)

The log is short but obscure. The process paused a few times, with the
percentage not changing in the usual 1:16 minute:seconds, and I think
that means it's fixing something or it imcorrecty predicted the
percentages. :

2020-06-27 20:51:00, Info CSI 00000001 Shim
considered
[l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.329_non e_e77145332606deb0\wcp.dll'
: got STATUS_OBJECT_PATH_NOT_FOUND
2020-06-27 20:51:00, Info CSI 00000002 Shim
considered
[l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.329_non e_e77145332606deb0\wcp.dll'
: got STATUS_SUCCESS
2020-06-27 20:51:01, Info DISM DISM Package Manager:
PID=12544 TID=12652 Loaded servicing stack for online use only. -
CDISMPackageManager::CreateCbsSession
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Found the OSServices. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderSto:Final_OnDisconnect
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Found the OSServices. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderSto:Final_OnDisconnect
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Found the PE Provider. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderSto:Final_OnDisconnect
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(DISM Package
Manager) - CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Package Manager:
PID=12544 TID=12652 Finalizing CBS core. - CDISMPackageManager::Finalize
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: DISM Package Manager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(MsiManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: MsiManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(IntlManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: IntlManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(IBSManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: IBSManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(DriverManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: DriverManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(DISM Unattend
Manager) - CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: DISM Unattend Manager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(SmiManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: SmiManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(AppxManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: AppxManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(ProvManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: ProvManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(AssocManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: AssocManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(GenericManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: GenericManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing
provider(OfflineSetupManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: OfflineSetupManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(SysprepManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: SysprepManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing provider(Edition Manager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: Edition Manager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Finalizing the servicing
provider(SetupPlatformManager) -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: SetupPlatformManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Releasing the local reference to OSServices. -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Disconnecting Provider: OSServices -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12544 TID=12652 Releasing the local reference to DISMLogger. Stop
logging. - CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Manager:
PID=12420 TID=12424 Closing session event handle 0x228 -
CDISMManager::CleanupImageSessionEntry
2020-06-27 20:51:01, Info DISM DISM.EXE: Image
session has been closed. Reboot required=no.
2020-06-27 20:51:01, Info DISM DISM.EXE:
2020-06-27 20:51:01, Info DISM DISM.EXE: -----
Ending Dism.exe session -----
2020-06-27 20:51:01, Info DISM DISM.EXE:
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12420 TID=12424 Found the OSServices. Waiting to finalize it until
all other providers are unloaded. -
CDISMProviderSto:Final_OnDisconnect
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12420 TID=12424 Disconnecting Provider: FolderManager -
CDISMProviderSto:Internal_DisconnectProvider
2020-06-27 20:51:01, Info DISM DISM Provider Sto
PID=12420 TID=12424 Releasing the local reference to DISMLogger. Stop
logging. - CDISMProviderSto:Internal_DisconnectProvider



*******

SFC is a troublemaker, and getting the thing pointed
at the right stuff is a pain.

http://winaero.com/blog/how-to-run-t...does-not-boot/

"sfc /scannow /offbootdir=C:\ /offwindir=D:\Windows

Note that offbootdir contains the letter of your "System Reserved"
partition and offwindir is the volume on which your broken,
unbootable Windows 10 is located.
"

Paul