Dell L502X win 10 drivers

On Sat, 24 Nov 2018 13:12:51 +0000, Dan wrote:

Thanks again.


You quoted umpteen lines of text just to add a two-word reply at the
end!

Please don't do that. None of us wants to scroll through all that just
to see what you wrote. Trim the quote appropriately. Quote only what
you are replying to (as I did above). In this case, Paul's last
paragraph would have been more than sufficient.

And the same with the two other replies in this thread that I see you
wrote today.

"Ken Blake" wrote:
You quoted umpteen lines of text just to add a two-word reply at the
end!

Please don't do that. None of us wants to scroll through all that just
to see what you wrote. Trim the quote appropriately. Quote only what
you are replying to (as I did above). In this case, Paul's last
paragraph would have been more than sufficient.

Well said.

And the same with the two other replies in this thread that I see you
wrote today.

The same goes for Paul in this thread. The replies have been getting
longer and longer with no one trimming anything. The same also applies
to several other posters in this and related groups. Trim quoted text!

On Sat, 24 Nov 2018 15:58:10 -0000, "Apd" wrote:

"Ken Blake" wrote:
You quoted umpteen lines of text just to add a two-word reply at the
end!

Please don't do that. None of us wants to scroll through all that just
to see what you wrote. Trim the quote appropriately. Quote only what
you are replying to (as I did above). In this case, Paul's last
paragraph would have been more than sufficient.

Well said.

And the same with the two other replies in this thread that I see you
wrote today.

The same goes for Paul in this thread. The replies have been getting
longer and longer with no one trimming anything. The same also applies
to several other posters in this and related groups. Trim quoted text!



Hello,

I imaged my Win 7 64 Ultimate installation. Put in my recovery Win 10
pro DVD to the inbuilt DVD drive. I get these options:

Choose language - highlighted to en US, then choose your keyboard
layout, I choose UK, then troubleshoot with options:
reset your PC / see advanced options.
Or
turn off your PC.
In the troubleshoot your options, I get:
reset your PC / lets you choose to keep or remove your files and then
reinstall windows -- I choose this option and the circulating circle
counts down a numerical percentage.
Then the computer reboots after reaching 100%.
I take out the DVD, and onscreen it says: operation system not found.

I have used Linux Mint 19 64 system tools such as gparted to look at
the SSD. It has a Windows install that looks not like my Win 7 64
Ultimate.

How do I get Win 10 pro to start up?

Dan wrote:

Hello,

I imaged my Win 7 64 Ultimate installation. Put in my recovery Win 10
pro DVD to the inbuilt DVD drive. I get these options:

Choose language - highlighted to en US, then choose your keyboard
layout, I choose UK, then troubleshoot with options:
reset your PC / see advanced options.
Or
turn off your PC.
In the troubleshoot your options, I get:
reset your PC / lets you choose to keep or remove your files and then
reinstall windows -- I choose this option and the circulating circle
counts down a numerical percentage.
Then the computer reboots after reaching 100%.
I take out the DVD, and onscreen it says: operation system not found.

I have used Linux Mint 19 64 system tools such as gparted to look at
the SSD. It has a Windows install that looks not like my Win 7 64
Ultimate.

How do I get Win 10 pro to start up?

Your situation is unique, in the sense you're in the middle of
an install. An article like this gives sage advice for an
*existing* install, and how to deal with the issue. Presumably
your issue is similar, but might not be exactly the same. For
example, if a person were to use "bootrec", is enough of
an OS present for that to work ? Probably not. The installer in
Windows, has probably fiddled around with the BCD anyway, and
it may not be an actual standard setup. This helps the installer
brush aside distractions, when it forces its way, and then
rolls back or fixes things up later.

https://www.makeuseof.com/tag/operat...not-found-fix/

Part of the problem could be UEFI/CSM/SecureBoot and what
exact mode did you use to boot the DVD when starting the
Clean Install. If I use the Popup Boot (F8 on my Asus),
it lists DVD (legacy) and DVD (UEFI). I select UEFI if
I want a UEFI installation to be done. The boot materials
are slightly different in that case. The UEFI option allows
a Secure Boot installation to be done, which might be a
reason for heading that way. A second reason for using UEFI,
would be so the disk could be GPT partitioned - this allows
the boot disk to be 2.2TB in size and provide all of its
available space for storage purposes. A legacy install
would be limited to 2.2TB.

The message you're seeing, could be coming from the MBR.
In the 440 byte boot section.

The MBR should recognize the "Active" partition, the one
with the boot flag set. If there's no boot flag set, that
would be a problem. If the Active partition didn't receive
a partition boot sector (around two or three sectors of
stuff actually), then that would stop it dead too.

But at a guess, you're missing the Active (boot) flag. You might
be able to see that with your Linux LiveCD. A Linux MBR doesn't
use the boot flag, but Windows does.

Also, when you report errors like this, it pays to *precisely*
report the words on the screen. Don't paraphrase them. Record
verbatim what it says. Windows 10 is such a pig, it can automatically
reboot before you've had a chance to write it down.

For your enjoyment, look at Figure 3 here. It shows
the MBR. It shows the three text strings the MBR can return
if things don't go well. See if the messages match what
you reported or not. If there is no match, post back
with the exact string, so I don't lead you astray.
The Vista MBR should be very similar to the Win10 one,
and using this as a reference is faster than me taking
a screenshot on the test machine.

https://thestarman.pcministry.com/asm/mbr/VistaMBR.htm

Paul

On Sun, 25 Nov 2018 17:50:06 -0500, Paul
wrote:

Dan wrote:

Hello,

I imaged my Win 7 64 Ultimate installation. Put in my recovery Win 10
pro DVD to the inbuilt DVD drive. I get these options:

Choose language - highlighted to en US, then choose your keyboard
layout, I choose UK, then troubleshoot with options:
reset your PC / see advanced options.
Or
turn off your PC.
In the troubleshoot your options, I get:
reset your PC / lets you choose to keep or remove your files and then
reinstall windows -- I choose this option and the circulating circle
counts down a numerical percentage.
Then the computer reboots after reaching 100%.
I take out the DVD, and onscreen it says: operation system not found.

I have used Linux Mint 19 64 system tools such as gparted to look at
the SSD. It has a Windows install that looks not like my Win 7 64
Ultimate.

How do I get Win 10 pro to start up?

Your situation is unique, in the sense you're in the middle of
an install. An article like this gives sage advice for an
*existing* install, and how to deal with the issue. Presumably
your issue is similar, but might not be exactly the same. For
example, if a person were to use "bootrec", is enough of
an OS present for that to work ? Probably not. The installer in
Windows, has probably fiddled around with the BCD anyway, and
it may not be an actual standard setup. This helps the installer
brush aside distractions, when it forces its way, and then
rolls back or fixes things up later.

https://www.makeuseof.com/tag/operat...not-found-fix/

Part of the problem could be UEFI/CSM/SecureBoot and what
exact mode did you use to boot the DVD when starting the
Clean Install. If I use the Popup Boot (F8 on my Asus),
it lists DVD (legacy) and DVD (UEFI). I select UEFI if
I want a UEFI installation to be done. The boot materials
are slightly different in that case. The UEFI option allows
a Secure Boot installation to be done, which might be a
reason for heading that way. A second reason for using UEFI,
would be so the disk could be GPT partitioned - this allows
the boot disk to be 2.2TB in size and provide all of its
available space for storage purposes. A legacy install
would be limited to 2.2TB.

The message you're seeing, could be coming from the MBR.
In the 440 byte boot section.

The MBR should recognize the "Active" partition, the one
with the boot flag set. If there's no boot flag set, that
would be a problem. If the Active partition didn't receive
a partition boot sector (around two or three sectors of
stuff actually), then that would stop it dead too.

But at a guess, you're missing the Active (boot) flag. You might
be able to see that with your Linux LiveCD. A Linux MBR doesn't
use the boot flag, but Windows does.

Also, when you report errors like this, it pays to *precisely*
report the words on the screen. Don't paraphrase them. Record
verbatim what it says. Windows 10 is such a pig, it can automatically
reboot before you've had a chance to write it down.

For your enjoyment, look at Figure 3 here. It shows
the MBR. It shows the three text strings the MBR can return
if things don't go well. See if the messages match what
you reported or not. If there is no match, post back
with the exact string, so I don't lead you astray.
The Vista MBR should be very similar to the Win10 one,
and using this as a reference is faster than me taking
a screenshot on the test machine.

https://thestarman.pcministry.com/asm/mbr/VistaMBR.htm

Paul


https://www.makeuseof.com/tag/operat...not-found-fix/
I tried:
3. Fix the Boot Records

When it came to step 2, I was told that this cannot be done.


I tried:
5. Activate the Windows Partition

Cannot be done was the message.

On Mon, 26 Nov 2018 09:05:35 +0000, Dan wrote:

On Sun, 25 Nov 2018 17:50:06 -0500, Paul
wrote:

Dan wrote:

Hello,

I imaged my Win 7 64 Ultimate installation. Put in my recovery Win 10
pro DVD to the inbuilt DVD drive. I get these options:

Choose language - highlighted to en US, then choose your keyboard
layout, I choose UK, then troubleshoot with options:
reset your PC / see advanced options.
Or
turn off your PC.
In the troubleshoot your options, I get:
reset your PC / lets you choose to keep or remove your files and then
reinstall windows -- I choose this option and the circulating circle
counts down a numerical percentage.
Then the computer reboots after reaching 100%.
I take out the DVD, and onscreen it says: operation system not found.

I have used Linux Mint 19 64 system tools such as gparted to look at
the SSD. It has a Windows install that looks not like my Win 7 64
Ultimate.

How do I get Win 10 pro to start up?

Your situation is unique, in the sense you're in the middle of
an install. An article like this gives sage advice for an
*existing* install, and how to deal with the issue. Presumably
your issue is similar, but might not be exactly the same. For
example, if a person were to use "bootrec", is enough of
an OS present for that to work ? Probably not. The installer in
Windows, has probably fiddled around with the BCD anyway, and
it may not be an actual standard setup. This helps the installer
brush aside distractions, when it forces its way, and then
rolls back or fixes things up later.

https://www.makeuseof.com/tag/operat...not-found-fix/

Part of the problem could be UEFI/CSM/SecureBoot and what
exact mode did you use to boot the DVD when starting the
Clean Install. If I use the Popup Boot (F8 on my Asus),
it lists DVD (legacy) and DVD (UEFI). I select UEFI if
I want a UEFI installation to be done. The boot materials
are slightly different in that case. The UEFI option allows
a Secure Boot installation to be done, which might be a
reason for heading that way. A second reason for using UEFI,
would be so the disk could be GPT partitioned - this allows
the boot disk to be 2.2TB in size and provide all of its
available space for storage purposes. A legacy install
would be limited to 2.2TB.

The message you're seeing, could be coming from the MBR.
In the 440 byte boot section.

The MBR should recognize the "Active" partition, the one
with the boot flag set. If there's no boot flag set, that
would be a problem. If the Active partition didn't receive
a partition boot sector (around two or three sectors of
stuff actually), then that would stop it dead too.

But at a guess, you're missing the Active (boot) flag. You might
be able to see that with your Linux LiveCD. A Linux MBR doesn't
use the boot flag, but Windows does.

Also, when you report errors like this, it pays to *precisely*
report the words on the screen. Don't paraphrase them. Record
verbatim what it says. Windows 10 is such a pig, it can automatically
reboot before you've had a chance to write it down.

For your enjoyment, look at Figure 3 here. It shows
the MBR. It shows the three text strings the MBR can return
if things don't go well. See if the messages match what
you reported or not. If there is no match, post back
with the exact string, so I don't lead you astray.
The Vista MBR should be very similar to the Win10 one,
and using this as a reference is faster than me taking
a screenshot on the test machine.

https://thestarman.pcministry.com/asm/mbr/VistaMBR.htm

Paul


https://www.makeuseof.com/tag/operat...not-found-fix/
I tried:
3. Fix the Boot Records

When it came to step 2, I was told that this cannot be done.


I tried:
5. Activate the Windows Partition

Cannot be done was the message.


I forgot to add, I downloaded Win 10 1809 iso, burnt and verified copy
via cdburnerxp and tried the recovery options, nothing worked.

Dan wrote:

https://www.makeuseof.com/tag/operat...not-found-fix/
I tried:
3. Fix the Boot Records

When it came to step 2, I was told that this cannot be done.


I tried:
5. Activate the Windows Partition

Cannot be done was the message.


I forgot to add, I downloaded Win 10 1809 iso, burnt and verified copy
via cdburnerxp and tried the recovery options, nothing worked.

Here's a link to what the drive looked like when you got the laptop.
Or at least, it's a place to start. Another thread claimed there
were more partitions.

https://superuser.com/questions/3130...rive-partition

*******

I experimented with my "recoverydisk" USB stick here.

I booted the stick in UEFI mode, from the popup boot menu,
and tried to restore the OS. The operation failed.

If I go to the recovery media and look in

sources\$PBR_Diskpart.txt

I see this...

rem == ResetPartitions-BIOS.txt ==
convert mbr
rem == 1. System partition =========================
create partition primary size=100
format quick fs=ntfs label="System"
assign letter="S"
active
rem == 2. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools partition ===
shrink minimum=450
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 3. Windows RE tools partition ===============
create partition primary
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
set id=0x27
list volume
exit

So the "layout" of the recovery is declared right on the media.
You could look in the "sources" folder on the DVD, for that file.
Translating the diskpart script above into english, it looks like:

+-----+------------------------+------------------------------+---------------------------+
| MBR | System 100MB (active) | Windows C: (size minus 450) | Windows RE tools 450MB |
+-----+------------------------+------------------------------+---------------------------+
system,active boot WinRE.wim bootable 380MB

OK, so when I boot the media in UEFI mode and say "recover",
the System partition is empty. No boot folder. No BCD file.
The message on boot is:

"An operating system wasn't found. Try disconnecting any drives
that don't contain an operating system."

That's not an MBR message. I don't know where that is coming
from, unless it's the PBR of the System 100MB partition. The PBR
might have been populated, before the recoverydrive installer
logic failed.

You *cannot* repair Windows if that partition is empty.
The repair process needs a source of the files to do the
repair. Maybe a real installer DVD could do it, but my
materials could not. I didn't waste a lot of time on
this, because "it's just not right".

*******

Next, I booted my media in Legacy (MSDOS) mode. The
restore populated all the folders.

Your $PBR_Diskpart.txt will have a different "recipe" being
fed to Diskpart than mine does. Consequently, there is a
low probability of you having three partitions as in
my example above.

This is my conditions, just after the installer unpacks
the media onto the hard drive, but before the first reboot
has a chance to take place.

https://i.postimg.cc/MT3fwGq6/system-folder.gif

https://i.postimg.cc/HLpr7MLW/C-Partition.gif

https://i.postimg.cc/VsSWNxTG/recovery.gif

While I've been typing this, Cortana is yapping at me,
so it's time to enter my details and local account
for login.

Paul

On Mon, 26 Nov 2018 11:46:27 -0500, Paul
wrote:

Dan wrote:

https://www.makeuseof.com/tag/operat...not-found-fix/
I tried:
3. Fix the Boot Records

When it came to step 2, I was told that this cannot be done.


I tried:
5. Activate the Windows Partition

Cannot be done was the message.


I forgot to add, I downloaded Win 10 1809 iso, burnt and verified copy
via cdburnerxp and tried the recovery options, nothing worked.

Here's a link to what the drive looked like when you got the laptop.
Or at least, it's a place to start. Another thread claimed there
were more partitions.

https://superuser.com/questions/3130...rive-partition

*******

I experimented with my "recoverydisk" USB stick here.

I booted the stick in UEFI mode, from the popup boot menu,
and tried to restore the OS. The operation failed.

If I go to the recovery media and look in

sources\$PBR_Diskpart.txt

I see this...

rem == ResetPartitions-BIOS.txt ==
convert mbr
rem == 1. System partition =========================
create partition primary size=100
format quick fs=ntfs label="System"
assign letter="S"
active
rem == 2. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery tools partition ===
shrink minimum=450
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem == 3. Windows RE tools partition ===============
create partition primary
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
set id=0x27
list volume
exit

So the "layout" of the recovery is declared right on the media.
You could look in the "sources" folder on the DVD, for that file.
Translating the diskpart script above into english, it looks like:

+-----+------------------------+------------------------------+---------------------------+
| MBR | System 100MB (active) | Windows C: (size minus 450) | Windows RE tools 450MB |
+-----+------------------------+------------------------------+---------------------------+
system,active boot WinRE.wim bootable 380MB

OK, so when I boot the media in UEFI mode and say "recover",
the System partition is empty. No boot folder. No BCD file.
The message on boot is:

"An operating system wasn't found. Try disconnecting any drives
that don't contain an operating system."

That's not an MBR message. I don't know where that is coming
from, unless it's the PBR of the System 100MB partition. The PBR
might have been populated, before the recoverydrive installer
logic failed.

You *cannot* repair Windows if that partition is empty.
The repair process needs a source of the files to do the
repair. Maybe a real installer DVD could do it, but my
materials could not. I didn't waste a lot of time on
this, because "it's just not right".

*******

Next, I booted my media in Legacy (MSDOS) mode. The
restore populated all the folders.

Your $PBR_Diskpart.txt will have a different "recipe" being
fed to Diskpart than mine does. Consequently, there is a
low probability of you having three partitions as in
my example above.

This is my conditions, just after the installer unpacks
the media onto the hard drive, but before the first reboot
has a chance to take place.

https://i.postimg.cc/MT3fwGq6/system-folder.gif

https://i.postimg.cc/HLpr7MLW/C-Partition.gif

https://i.postimg.cc/VsSWNxTG/recovery.gif

While I've been typing this, Cortana is yapping at me,
so it's time to enter my details and local account
for login.

Paul


Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.

Dan wrote:


Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.

The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul

On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:


Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.

The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul


Thank you Paul. SSD is visible in the bios. I have had a very heavy
day. I will try this on Tuesday and get back to you.

On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:


Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.

The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul

Hello Paul,

I have tried this, but still nothing works when I try to install from
the Dell Win 10 64 pro recovery DVD. I still cannot boot to Windows.
AOMEI partition manager sees a Win 10 install, but cannot fix
anything.

If I install from version 1809, it boots fine. But when I finish
installing all the drivers, I get 100% cpu from system and nvidia
container.

What else can I do?

Dan wrote:
On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:

Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.
The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul

Hello Paul,

I have tried this, but still nothing works when I try to install from
the Dell Win 10 64 pro recovery DVD. I still cannot boot to Windows.
AOMEI partition manager sees a Win 10 install, but cannot fix
anything.

If I install from version 1809, it boots fine. But when I finish
installing all the drivers, I get 100% cpu from system and nvidia
container.

What else can I do?

Yes, I caught sight of that NVidia container thing just a
day or two ago, when installing a new video card. I think
NVidia might have even created its own account for that.

https://www.howtogeek.com/343120/wha...he-background/

I tried to install just the "driver", but the installer just
ignores your tick box settings and does whatever it feels like.

I think I may have avoided GeForce Experience, but I can't be sure.

Since I sucked in crap by doing that (378.78 driver on CD),
and got more than the driver, I had to retaliate.

This is on a Windows 10, where I haven't made adjustments yet.

https://i.postimg.cc/rw0s9gp1/nvidia...uled-tasks.gif

I tried to leave just the crash monitors running, but may have
to remove these if there is trouble. This is a second Win10
install on a scratch drive.

https://i.postimg.cc/Kv6zYBZJ/nvidia...h-monitors.gif

On this latest picture, when I booted the machine I got
a code 43 on the video card in Device Manager, and had to
disable an AMD service (services.msc) that didn't seem to get removed
with its driver removal. A reboot after that, and the
Nvidia driver loaded. But it could just as easily
be the Task Scheduler edits I did. I've only had
this config for a short time, and I'm still playing
with it.

Usually when a bumbling software company resorts to this
sort of thing, if you say, run their control panel,
they'll then march into the Task Scheduler and un****
your customizations. Sorta like a malware would do. It
remains to be seen how many tricks are present here,
how many couplings, entanglements, and so on, are present.

Lots more experiments to do.

Remember, you didn't buy a product, you "bought an adventure" :-(
Like the tourist who went hang gliding and the operator
forgot to clip his harness to the glider. The guy survived,
and ended up with a broken wrist, a titanium plate, and screws.
But he'll be telling that story for the rest of his life.

Paul

On Sun, 02 Dec 2018 12:10:10 -0500, Paul
wrote:

Dan wrote:
On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:

Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.
The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul

Hello Paul,

I have tried this, but still nothing works when I try to install from
the Dell Win 10 64 pro recovery DVD. I still cannot boot to Windows.
AOMEI partition manager sees a Win 10 install, but cannot fix
anything.

If I install from version 1809, it boots fine. But when I finish
installing all the drivers, I get 100% cpu from system and nvidia
container.

What else can I do?

Yes, I caught sight of that NVidia container thing just a
day or two ago, when installing a new video card. I think
NVidia might have even created its own account for that.

https://www.howtogeek.com/343120/wha...he-background/

I tried to install just the "driver", but the installer just
ignores your tick box settings and does whatever it feels like.

I think I may have avoided GeForce Experience, but I can't be sure.

Since I sucked in crap by doing that (378.78 driver on CD),
and got more than the driver, I had to retaliate.

This is on a Windows 10, where I haven't made adjustments yet.

https://i.postimg.cc/rw0s9gp1/nvidia...uled-tasks.gif

I tried to leave just the crash monitors running, but may have
to remove these if there is trouble. This is a second Win10
install on a scratch drive.

https://i.postimg.cc/Kv6zYBZJ/nvidia...h-monitors.gif

On this latest picture, when I booted the machine I got
a code 43 on the video card in Device Manager, and had to
disable an AMD service (services.msc) that didn't seem to get removed
with its driver removal. A reboot after that, and the
Nvidia driver loaded. But it could just as easily
be the Task Scheduler edits I did. I've only had
this config for a short time, and I'm still playing
with it.

Usually when a bumbling software company resorts to this
sort of thing, if you say, run their control panel,
they'll then march into the Task Scheduler and un****
your customizations. Sorta like a malware would do. It
remains to be seen how many tricks are present here,
how many couplings, entanglements, and so on, are present.

Lots more experiments to do.

Remember, you didn't buy a product, you "bought an adventure" :-(
Like the tourist who went hang gliding and the operator
forgot to clip his harness to the glider. The guy survived,
and ended up with a broken wrist, a titanium plate, and screws.
But he'll be telling that story for the rest of his life.

Paul


Cheers Paul,

why is 10 so difficult to deal with? This is just food for Apple, as
Mac's are going to do so well once Win 7 in 2020 gets no more support
as Apple is going to make a fortune over this. I own a iPod, that is
only the Apple product I use.
Really, I just want to use my laptop without my CPU working at 100%.
I just installed the driver, re-booted and my CPU has gone into over
drive.
My SSD, who really know how much more will it take, since I
re-installed Win 10 64 1809 and tried so many time to install win 10
pro 64 from a Dell DVD with no success.
I don't really know what else I can do.

Dan wrote:
On Sun, 02 Dec 2018 12:10:10 -0500, Paul
wrote:

Dan wrote:
On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:

Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.
The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul
Hello Paul,

I have tried this, but still nothing works when I try to install from
the Dell Win 10 64 pro recovery DVD. I still cannot boot to Windows.
AOMEI partition manager sees a Win 10 install, but cannot fix
anything.

If I install from version 1809, it boots fine. But when I finish
installing all the drivers, I get 100% cpu from system and nvidia
container.

What else can I do?
Yes, I caught sight of that NVidia container thing just a
day or two ago, when installing a new video card. I think
NVidia might have even created its own account for that.

https://www.howtogeek.com/343120/wha...he-background/

I tried to install just the "driver", but the installer just
ignores your tick box settings and does whatever it feels like.

I think I may have avoided GeForce Experience, but I can't be sure.

Since I sucked in crap by doing that (378.78 driver on CD),
and got more than the driver, I had to retaliate.

This is on a Windows 10, where I haven't made adjustments yet.

https://i.postimg.cc/rw0s9gp1/nvidia...uled-tasks.gif

I tried to leave just the crash monitors running, but may have
to remove these if there is trouble. This is a second Win10
install on a scratch drive.

https://i.postimg.cc/Kv6zYBZJ/nvidia...h-monitors.gif

On this latest picture, when I booted the machine I got
a code 43 on the video card in Device Manager, and had to
disable an AMD service (services.msc) that didn't seem to get removed
with its driver removal. A reboot after that, and the
Nvidia driver loaded. But it could just as easily
be the Task Scheduler edits I did. I've only had
this config for a short time, and I'm still playing
with it.

Usually when a bumbling software company resorts to this
sort of thing, if you say, run their control panel,
they'll then march into the Task Scheduler and un****
your customizations. Sorta like a malware would do. It
remains to be seen how many tricks are present here,
how many couplings, entanglements, and so on, are present.

Lots more experiments to do.

Remember, you didn't buy a product, you "bought an adventure" :-(
Like the tourist who went hang gliding and the operator
forgot to clip his harness to the glider. The guy survived,
and ended up with a broken wrist, a titanium plate, and screws.
But he'll be telling that story for the rest of his life.

Paul


Cheers Paul,

why is 10 so difficult to deal with? This is just food for Apple, as
Mac's are going to do so well once Win 7 in 2020 gets no more support
as Apple is going to make a fortune over this. I own a iPod, that is
only the Apple product I use.
Really, I just want to use my laptop without my CPU working at 100%.
I just installed the driver, re-booted and my CPU has gone into over
drive.
My SSD, who really know how much more will it take, since I
re-installed Win 10 64 1809 and tried so many time to install win 10
pro 64 from a Dell DVD with no success.
I don't really know what else I can do.

Can you give me a screen shot of the NVidia section of
your Task Manager ?

Even if you sort Task Manager alphabetically, it doesn't
stand still long enough to fire the SnippingTool at
just the right time. It'll take a few tries to get
a nicely curated view.

You might also be able to use Process Explorer, and list the
nvcontainer and get some details about what is inside.

This is like Task Manager, only you can extract more details.
If you run the executable as Administrator, it will add
some details about threads. It needs elevation to look inside
stuff.

https://docs.microsoft.com/en-us/sys...ocess-explorer

*******

It's shadowplay here. That was an nvcontainer running off the rails.

https://forums.geforce.com/default/t...igh-cpu-usage/

The NVContainer is a toy, to enhance lock-in on programs.
The same thing as happens, when a developer selects CUDA
instead of OpenCL.

https://developer.nvidia.com/nvidia-container-runtime

GeForce Experience can scan the C: drive.

https://www.reddit.com/r/nvidia/comm...accessing_all/

Like this page, I tried to install just the driver, and
it didn't stop at that.

https://www.lifehacker.com.au/2016/0...ull-never-use/

And once installed, Brink turned off some of the stuff.
Since I didn't have Geforce Experience ticked, not all
of these showed up.

https://www.ghacks.net/2015/12/27/di...d-performance/

*******

Try and collect data first, as best you can.

Task Manager or Process Explorer might help.

*******

For your brand of SSD, install the "Toolkit" that comes
with it, then look for the SMART readout. There is usually
a derived quantity like "wear life" that gives a percentage
of how much SSD is left.

For some hardware brands of SSDs, you have to go to their
web site to find the Toolbox. Many of the toolboxes are
crap, and the features don't work all that well. But,
that's what they have to offer. For example, the Corsair
Neutron I bought, the Toolbox actually worked - who
would have suspected that ? When the big_name toolboxes,
don't.

Paul

On Sun, 02 Dec 2018 14:03:44 -0500, Paul
wrote:

Dan wrote:
On Sun, 02 Dec 2018 12:10:10 -0500, Paul
wrote:

Dan wrote:
On Mon, 26 Nov 2018 13:34:52 -0500, Paul
wrote:

Dan wrote:

Cheers Paul.

I have downloaded Win 10 64 1809 using MediaCreationTool1809.exe from
Microsoft. When I tried to repair the installation with this, I got
this:

"a required device isn't connected or can't be accessed
error code 0xc000000f"
"Press F8 or press enter to try again"

Used Linux Mint 19 64 to see if the SSD was visible under Linux, which
was GPT after using the Dell Win 10 64 DVD. I used aomei partition
assistant boot CD to format the SSD.
Win 10 64 ver 1809 installed perfectly and I got all, bar one of the
drivers installed. According to device manager one 'pci hardware' is
missing. I used wsus offline to update the fresh install.
This shows that there is nothing wrong with my SSD or computer.
The 0xc000000f is similar to my error, in that the /boot or BCD
file might not be present on the partition marked as Active.

https://neosmart.net/wiki/0xc000000f...guration-data/

Paul
Hello Paul,

I have tried this, but still nothing works when I try to install from
the Dell Win 10 64 pro recovery DVD. I still cannot boot to Windows.
AOMEI partition manager sees a Win 10 install, but cannot fix
anything.

If I install from version 1809, it boots fine. But when I finish
installing all the drivers, I get 100% cpu from system and nvidia
container.

What else can I do?
Yes, I caught sight of that NVidia container thing just a
day or two ago, when installing a new video card. I think
NVidia might have even created its own account for that.

https://www.howtogeek.com/343120/wha...he-background/

I tried to install just the "driver", but the installer just
ignores your tick box settings and does whatever it feels like.

I think I may have avoided GeForce Experience, but I can't be sure.

Since I sucked in crap by doing that (378.78 driver on CD),
and got more than the driver, I had to retaliate.

This is on a Windows 10, where I haven't made adjustments yet.

https://i.postimg.cc/rw0s9gp1/nvidia...uled-tasks.gif

I tried to leave just the crash monitors running, but may have
to remove these if there is trouble. This is a second Win10
install on a scratch drive.

https://i.postimg.cc/Kv6zYBZJ/nvidia...h-monitors.gif

On this latest picture, when I booted the machine I got
a code 43 on the video card in Device Manager, and had to
disable an AMD service (services.msc) that didn't seem to get removed
with its driver removal. A reboot after that, and the
Nvidia driver loaded. But it could just as easily
be the Task Scheduler edits I did. I've only had
this config for a short time, and I'm still playing
with it.

Usually when a bumbling software company resorts to this
sort of thing, if you say, run their control panel,
they'll then march into the Task Scheduler and un****
your customizations. Sorta like a malware would do. It
remains to be seen how many tricks are present here,
how many couplings, entanglements, and so on, are present.

Lots more experiments to do.

Remember, you didn't buy a product, you "bought an adventure" :-(
Like the tourist who went hang gliding and the operator
forgot to clip his harness to the glider. The guy survived,
and ended up with a broken wrist, a titanium plate, and screws.
But he'll be telling that story for the rest of his life.

Paul


Cheers Paul,

why is 10 so difficult to deal with? This is just food for Apple, as
Mac's are going to do so well once Win 7 in 2020 gets no more support
as Apple is going to make a fortune over this. I own a iPod, that is
only the Apple product I use.
Really, I just want to use my laptop without my CPU working at 100%.
I just installed the driver, re-booted and my CPU has gone into over
drive.
My SSD, who really know how much more will it take, since I
re-installed Win 10 64 1809 and tried so many time to install win 10
pro 64 from a Dell DVD with no success.
I don't really know what else I can do.

Can you give me a screen shot of the NVidia section of
your Task Manager ?

Even if you sort Task Manager alphabetically, it doesn't
stand still long enough to fire the SnippingTool at
just the right time. It'll take a few tries to get
a nicely curated view.

You might also be able to use Process Explorer, and list the
nvcontainer and get some details about what is inside.

This is like Task Manager, only you can extract more details.
If you run the executable as Administrator, it will add
some details about threads. It needs elevation to look inside
stuff.

https://docs.microsoft.com/en-us/sys...ocess-explorer

*******

It's shadowplay here. That was an nvcontainer running off the rails.

https://forums.geforce.com/default/t...igh-cpu-usage/

The NVContainer is a toy, to enhance lock-in on programs.
The same thing as happens, when a developer selects CUDA
instead of OpenCL.

https://developer.nvidia.com/nvidia-container-runtime

GeForce Experience can scan the C: drive.

https://www.reddit.com/r/nvidia/comm...accessing_all/

Like this page, I tried to install just the driver, and
it didn't stop at that.

https://www.lifehacker.com.au/2016/0...ull-never-use/

And once installed, Brink turned off some of the stuff.
Since I didn't have Geforce Experience ticked, not all
of these showed up.

https://www.ghacks.net/2015/12/27/di...d-performance/

*******

Try and collect data first, as best you can.

Task Manager or Process Explorer might help.

*******

For your brand of SSD, install the "Toolkit" that comes
with it, then look for the SMART readout. There is usually
a derived quantity like "wear life" that gives a percentage
of how much SSD is left.

For some hardware brands of SSDs, you have to go to their
web site to find the Toolbox. Many of the toolboxes are
crap, and the features don't work all that well. But,
that's what they have to offer. For example, the Corsair
Neutron I bought, the Toolbox actually worked - who
would have suspected that ? When the big_name toolboxes,
don't.

Paul

OK. Paul I finally got Windows 10 64 1809 installed and working on the
laptop.

I formatted, re - installed Win 7 64 ultimate from my Dell recovery
DVD. Then, re - installed all the drivers and then ran Windows update.
Used portable ccleaner to remove all temp files and then rebooted.
Once back into Win 7 64 Ultimate environment, I put the Win 10 pro 64
1809 into the DVD drive and ran 'setup.exe' which said if I want to
upgrade my Win 7 64. I proceeded to follow on screen and eventually
the different Windows environment of Win 10 64 pro came on screen.

I heard the laptops fan on all the time, then discovered that
'onedrive' was taking up 99.8% of my CPU time. I stopped it from task
manager and set it as to not start again.
Now ran Windows update, got all the updates and re - booted.
CPU time is no longer running at 99.8% and I have a working Win 10 64
pro 1809 laptop.
Now, my question is that I did not have to type in any information
regarding a COA, in Windows activation it states my Win 10 64 1809 is
activated but a 'digital license'.

How do I retrieve my Windows key if I need to re - install Win 10 pro?
Do I need to install Win 7 64 Ultimate then install Windows 10 pro
over it to get a fresh install of Win 10 pro?