Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Unattended Problem - Device Drivers?

Featured Replies

Hi all,

I am having a problem where the it says "setup restarting..." after the first reboot and then the screen just sits there blue. Eventually a windows error box comes up (after ages) saying Virtual Memory is too low and will now resize.. it immediately reboots and goes throught the whole thing again ... over & over

same thing happens to me when i use method 2


I got a new message this time "setup failed to start" at the same spot

error code 0xc000012d

I'm just curious, are you running a sata hd?

If you do, try to do the setup again on a normal ata hd with the same install cd. That way, I elliminated the cd as being the problem.

I've sent a PM to Pyron 9 days ago now... (21st of October), still no reply, he hasn't read it yet...

Anyone here who has the chance of notifying him?

Bâshrat the Sneaky

Guys with this error, are u using nLite? I tested my cd not until i tried method 2, and got the same rebooting crap. Finally it hit me to try out the iso before the driver packs and walla, same problem. I stopped using nLite and did the slipstreaming and reduction in size manually and then added the driver packs with method two and received no error. This could be an nLite issue. But hey, I dont know much and could be way off base.

-northofnowhere

I have problem with no restart problem after setup is finish

In "Presetup.cmd" section "Reset DriverPolicy" i changed folloving lines

REM +=======================================================+

REM | Reset DriverPolicy |

REM |-------------------------------------------------------|

reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1

reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1

reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01

REM +=======================================================+

into

REM +=======================================================+

REM | Reset DriverPolicy |

REM |-------------------------------------------------------|

reg add "HKCU\Software\Microsoft\Driver Signing" /v Policy /t REG_DWORD /d 1 /f

reg add "HKCU\Software\Policies\Microsoft\Windows NT\Driver Signing" /v BehaviorOnFailedVerify /t REG_DWORD /d 1 /f

reg add "HKLM\Software\Microsoft\Driver Signing" /v Policy /t REG_BINARY /d 01 /f

REM +=======================================================+

because this keys alredy exist in registry and requires confirmation parametar "/f"

so setup now close presetup.cmd and restart normaly.

thanks.

I forget to thank you for all your free time spend here. :hello:

Another thing:

If the setup freeze or power failure happen, setup go again after restart, but

then section after "start /WAIT setup.exe %*" in the "presetup.cmd" never be execute.

1. "Reset DriverPolicy" never be execute.

2. "Clenup" never be execute.

3. "Reset DevicePath" never be execute.

Will be better put that stuff somewhere in "RunOnceEx" section and execute them after restart.

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.