Windows 10 Pro x64 2004 On A P8400 CPU

Has anybody installed 2004 Pro x64 on a P8400 CPU? I keep getting a SAFE_OS
during BOOT operation error. Some internet messages point at the
mcupdate_GenuineIntel.dll. I assume this file has something to do with the
micro code in the CPU but not sure. I have tried everything including
formatting the harddrive so that it is a complete fresh install. I just got
done moving this computer from 1909 x86 to 1909 x64. So I was really
looking forward to rebuilding it a second time.
--
Bill

Brought to you from Anchorage, Alaska

On 6/24/20 1:11 PM, this is what Bill Bradshaw wrote:
So I was really looking forward to rebuilding it a second time.
You were?

Big Al wrote:
On 6/24/20 1:11 PM, this is what Bill Bradshaw wrote:
So I was really looking forward to rebuilding it a second time. You
were?

Yes, I was being sarcastic.

Bill

Bill Bradshaw wrote:
Has anybody installed 2004 Pro x64 on a P8400 CPU? I keep getting a SAFE_OS
during BOOT operation error. Some internet messages point at the
mcupdate_GenuineIntel.dll. I assume this file has something to do with the
micro code in the CPU but not sure. I have tried everything including
formatting the harddrive so that it is a complete fresh install. I just got
done moving this computer from 1909 x86 to 1909 x64. So I was really
looking forward to rebuilding it a second time.

Do you have an error code ?

Some of the error codes can be quite long: 0xc1900101 – 0x20017

I take it, this is how you determined mcupdate_GenuineIntel.dll
was at fault.

Are there any files like Setuperr.log and Setupact.log ?

https://support.microsoft.com/en-us/...sion-of-window

Paul

Paul wrote:
Bill Bradshaw wrote:
Has anybody installed 2004 Pro x64 on a P8400 CPU? I keep getting a
SAFE_OS during BOOT operation error. Some internet messages point
at the mcupdate_GenuineIntel.dll. I assume this file has something
to do with the micro code in the CPU but not sure. I have tried
everything including formatting the harddrive so that it is a
complete fresh install. I just got done moving this computer from
1909 x86 to 1909 x64. So I was really looking forward to rebuilding
it a second time.

Do you have an error code ?

Some of the error codes can be quite long: 0xc1900101 – 0x20017

I take it, this is how you determined mcupdate_GenuineIntel.dll
was at fault.

Are there any files like Setuperr.log and Setupact.log ?

https://support.microsoft.com/en-us/...sion-of-window

Paul

The error is 0xC1900101-0x20017 The installation failed in the SAFE_OS phase
with an error during BOOT operation.

I have been searching the internet and discused items was the
mcupdate_GenuineIntel.dll. Some of the proposed solutions are more than a
little concerning to me. I have looked at the Setuperr.log and Setupact.log
but do not know what to look for.

Setuperr.log

2020-06-17 09:14:03, Error MOUPG
CInstallUI::GetDefaultLanguage(2027): Result = 0x80070002[gle=0x00000002]
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::ConnectToSourceUrl(697): Result =
0x80072EE7[gle=0x00002ee7]
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::PrepareFile(764): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::TransferFile(932): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager:ownloadProductsXml(10451): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::ExecuteDownloadMode(8731): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::ExecuteDownlevelMode(405): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::GetDUSetupResults(6510): Result = 0x80070490
2020-06-17 09:14:05, Error MOUPG
CSetupManager::Execute(294): Result = 0x80072EE7
2020-06-17 09:14:05, Error MOUPG CSetupHost::Execute(433):
Result = 0x80072EE7
2020-06-17 09:14:05, Error MOUPG SetupHost: Diagnostic tool
does not exist [C:\$Windows.~WS\Sources\SetupDiag.exe][gle=0x00000002]
2020-06-17 09:14:05, Error MOUPG
CSetupHost::ExecuteDiagnosticAnalysis(1541): Result =
0x80070003[gle=0x00000002]

The Setupact.log is pretty long so I have not included it.

I guess I should look up some of these result codes.

Bill

On 24/06/2020 18:11, Bill Bradshaw wrote:
Has anybody installed 2004 Pro x64 on a P8400 CPU? I keep getting a SAFE_OS
during BOOT operation error.

Most of us here have installed it and we didn't have any errors. You
were told to do a clean install but because of your low intelligence you
decided not to follow our advice.Â* You are what we call in the IT
industry "ASK-HOLE".Â* You ask for advice but decide to do ignore all of
it do something really stupid.

You must be a "Red Indian" or indigenous person of USA who was spared
life because of your stupidityÂ* or somebody still living in an igloo.Â*
People don't normally kill stupid people because they are not likely
cause any serious problems like Negroes who are still demonstrating
their homo-sapien ancestry.



--
With over 1.2 billion devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

Bill Bradshaw wrote:
Paul wrote:
Bill Bradshaw wrote:
Has anybody installed 2004 Pro x64 on a P8400 CPU? I keep getting a
SAFE_OS during BOOT operation error. Some internet messages point
at the mcupdate_GenuineIntel.dll. I assume this file has something
to do with the micro code in the CPU but not sure. I have tried
everything including formatting the harddrive so that it is a
complete fresh install. I just got done moving this computer from
1909 x86 to 1909 x64. So I was really looking forward to rebuilding
it a second time.
Do you have an error code ?

Some of the error codes can be quite long: 0xc1900101 – 0x20017

I take it, this is how you determined mcupdate_GenuineIntel.dll
was at fault.

Are there any files like Setuperr.log and Setupact.log ?

https://support.microsoft.com/en-us/...sion-of-window

Paul

The error is 0xC1900101-0x20017 The installation failed in the SAFE_OS phase
with an error during BOOT operation.

I have been searching the internet and discused items was the
mcupdate_GenuineIntel.dll. Some of the proposed solutions are more than a
little concerning to me. I have looked at the Setuperr.log and Setupact.log
but do not know what to look for.

Setuperr.log

2020-06-17 09:14:03, Error MOUPG
CInstallUI::GetDefaultLanguage(2027): Result = 0x80070002[gle=0x00000002]
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::ConnectToSourceUrl(697): Result =
0x80072EE7[gle=0x00002ee7]
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::PrepareFile(764): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CDlpTransportHttp::TransferFile(932): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager:ownloadProductsXml(10451): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::ExecuteDownloadMode(8731): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::ExecuteDownlevelMode(405): Result = 0x80072EE7
2020-06-17 09:14:03, Error MOUPG
CSetupManager::GetDUSetupResults(6510): Result = 0x80070490
2020-06-17 09:14:05, Error MOUPG
CSetupManager::Execute(294): Result = 0x80072EE7
2020-06-17 09:14:05, Error MOUPG CSetupHost::Execute(433):
Result = 0x80072EE7
2020-06-17 09:14:05, Error MOUPG SetupHost: Diagnostic tool
does not exist [C:\$Windows.~WS\Sources\SetupDiag.exe][gle=0x00000002]
2020-06-17 09:14:05, Error MOUPG
CSetupHost::ExecuteDiagnosticAnalysis(1541): Result =
0x80070003[gle=0x00000002]

The Setupact.log is pretty long so I have not included it.

I guess I should look up some of these result codes.

Bill



https://docs.microsoft.com/en-gb/win...dy_UpgradeTips

https://docs.microsoft.com/en-gb/win...res#0xc1900101

"0xC1900101 is a generic rollback code, and usually indicates
that an incompatible driver is present. The incompatible driver
can cause blue screens, system hangs, and unexpected reboots.
Analysis of supplemental log files is often helpful, such as:

The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp,
Event logs: $Windows.~bt\Sources\Rollback*.evtx
The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.de v.log"

"0xC1900101 - 0x20017

A driver has caused an illegal operation.
Windows was not able to migrate the driver, resulting in a
rollback of the operating system.
This is a SafeOS boot failure, typically caused by drivers
or non-Microsoft disk encryption software."

Probably that last log, will be readable.

And there is this. But it might not be intended for that
particular failure phase.

https://docs.microsoft.com/en-gb/win...rade/setupdiag

Since Version 2004 has a copy on-board, then this should have been generated.

/Output: %windir%\logs\SetupDiag\SetupDiagResults.xml

Like most Microsoft materials of this sort, don't expect miracles.
Their parsing and event conversion stuff doesn't always work
worth a darn.

Paul