Софт-Архив

Starting windows

Рейтинг: 4.9/5.0 (1330 проголосовавших)

Описание

Вечная - Starting windows - Windows 7

Вечная "Starting windows" - Windows 7

25.10.2012, 20:08 Вечная "Starting windows"

Вот моя проблема:

Вчера установил на комп. винду с загрузочной флешки, вроде бы всё пошло нормально, всё установилось. Сегодня, включаю комп, а он собака дальше грузится логотипа виндовс не хочет, а да, когда устанавливал винду с флешки, так же комп проходила белая посла загрузки файлов и ставало на логотипе "Starting windows", где-то прочитал, что надо вытащить одну планку памяти, ну я вытащил и о, чудо, после той белой строки, проходит несколько секунд и пошла установка, ну я конечно же обрадовался, мол ура, наконец-то все проблемы решены, так вот возвращаемся к сегодня загрузка винды стоит на "starting windows", я опять полез вытаскивать планку одну, ноль эмоций, я эти две планки по очерёдно вставлял,но нифига, решил забить, потом поискав диск установочный, так как флешку я уже захламил всякими файлами, я подумал, что она уже не подойдёт. Засовываю диск, опять же грузится только до "starting windows", я опять вытаскиваю планку, ничего не происходит, я вообще опечалился и для контрольного раза решил еще раз включил, перед включением закинул планки память оперативной, и черт его дери, система запустилась, вот пишу вам с моего компа, который меня иногда просто ставит в ступор. Вопрос у меня таков, в какой аппаратной части могут быть проблемы, я грешу на оперативку, ах да вот мой комп:

Operating System: Windows 7 Максимальная 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)

BIOS: Award Modular BIOS v6.00PG

Processor: AMD Phenom(tm) II X2 550 Processor (2 CPUs),

Memory: 4096MB RAM

Available OS Memory: 4094MB RAM

Starting Windows:

  • скачать
  • скачать
  • Другие статьи, обзоры программ, новости

    При установке Windows 7 зависает на этапе Starting Windows

    При установке Windows 7 зависает на этапе Starting Windows

    Условие: мат плата GA-H55M-USB3. память кит две планки 2*4 ГБ Kingstone 1333. проц i3-540 (раньше стояла система похуже)

    Пытаюсь произвести установку Windows 7 64, однако после загрузки драйверов (серая полоска внизу) вылезает надпись Starting Windows без анимации и установка дальше не идет.

    Ранее стояла Windows 7 32 (устанавливал на старой системе), и она со старого диска запускается (все работает, игры приложения и так далее, только на 3,5 Гб памяти вместо 8), кроме того спокойно устанавливается Windows XP (тоже все работает).

    Прочитал кучу инфы в нете, вот что делал:

    - отключил флоппи дисковод 3,5

    - биос обновил

    - менял настройки биос (ACHI, IDE, legacy режим отключал и включал)

    - отключал жесткие и подключал по одному.

    Все бестолку. Единственное один глюк заметил (когда из комплекта "кит" памяти оставляю одну только в разъеме, происходит цикличная перезагрузка компа, ну как бы биос запускается и перезагрузка)

    Ребята помогите, целый день бился никак не одолею проблему.

    Starting windows вместо запуск windows

    starting windows вместо запуск windows

    Александр Знаток (413), на голосовании 2 года назад

    Друзья, всем привет. Как изменить надпись при включении компьютера starting windows на запуск windows. захожу в рабочий стол изменить надпись starting windows, и высвечивается ошибка ошибка при проверке winload.exe.mui он не является PE файлом. Что делать. И ВЛИЯЕТ ЛИ НА РАБОТУ И СКОРОСТЬ КОМПЬЮТЕРА?

    НЕ ПОМОГАЕТ.

    с помощью вот этого метода.

    Запустите командную строку от имени администратора и выполните 3 команды, после каждой нажимая "Ввод":

    cd / (сменить директорию, это на всякий случай, вдруг у вас откроется папка пользователя, как у меня)

    bcdedit /enum (будет показан список меню загрузки)

    bcdedit /set locale ru-RU (установить русский язык)

    Слово current на скрине в последней команде обвёл в рамку, т. к. не знаю, что будет написано у вас в строке идентификатор, что чуть выше на скрине. Что написано в строке идентификатор, то и прописывать в последнюю команду. ПОДСКАЖИТЕ ПЛИИИЗ.

    Решено зависает установка windows 7 64 при установке новой памяти

    Материнская плата Gigabyte ga-p55m-ud2 rev 1.0

    Процессор Core i3 530

    Старая память одна планка 2Гб

    Старая операционная система Windows XP sp3 32 bit

    Перечисленная конфигурация рабочая.

    Далее захотели добавить памяти до 16Гб и следовательно обновить ОС до windows 7 x64. Купили память, две планки Crusial bls8g3d1339ds1s00 по 8Гб. Установили в этот же системник вместо планки 2Гб. Старая система Windows xp 32 нормально работает, но, соответственно, видит 4Гб из 16.

    Далее загружаемся с диска Windows 7 x64. Установка не запускается, виснет в самом начале на надписи "Starting Windows", еще до анимации значка Windows. Также ведет себя установка windows server 2008 R2. Memtest разных версий или виснет через 2-3 секунды после запуска или уходит в ребут. При этом уставнока windows xp/2003 запускается и проходит тестовый этап, дальше не пробовал.

    Для теста все переферийные компоненты отключили. То есть только мать, проц, новая память. Блок питания 700Вт.

    Если поставить новую память в другой системник, память нормально работает(memtest).

    То есть память не работает именно в комбинации мати и проца. Вроде и мать и проц поддерживают память до 16Гб, или я не прав? На что еще обратить внимание/попробовать?

    Stuck on Starting Windows screen during install - Windows 7 Help Forums

    Stuck on 'Starting Windows' screen during install

    I've found others on the forum attempting the same thing as me, but with different problems. I'm hoping this isn't a duplicate.

    I recently purchased a Dell XPS 15 (l521x) that came with Windows 8. The system boots from the hard drive through UEFI by default, so I think the hard drive is already GPT. I am attempting to install Windows 7 from a UEFI bootable USB. The system goes through the 'copying files' phase and then goes to the Starting Windows screen. As the colored dots of the Windows logo are circling, the system freezes. Can someone help me fix this problem? The following are the steps I took in order to install Windows 7:

    - Made adjustments so that USB is UEFI bootable (efi/boot/bootx64.efi)

    - In BIOS, set SATA Operation to AHCI and disabled Secure Boot

    - Select USB drive from UEFI boot menu

    Many thanks in advance as I've been fighting with this for several weeks now.

    Windows 7 is stuck at - Starting Windows - when I attempt to boot computer - Super User

    Windows 7 is stuck at "Starting Windows" when I attempt to boot computer

    Basically, whenever I turn on my computer, it gets to the Starting Windows phase and just stays there. The startup animation still plays, yet it gets nowhere.

    I have tried booting into safe mode, however it gets stuck at loading CLASSPNP.SYS. It then freezes there and doesn't continue booting.

    I have tried booting into recovery mode from the hard drive, and it freezes after displaying the background image. I have tried booting from a recovery CD, which works, and I was able to use system restore. However, using system restore did not fix it, and it still is stuck at the Starting Windows screen.

    I have tried booting a Windows CD (Windows 8 Retail Installer) to see if I could upgrade it to fix this issue, however that froze at a blank screen after it got past the boot logo.

    I have tried changing around the BIOS settings (including resetting), to no avail.

    I have tried re-plugging the internal PSU cables (this is a custom-built desktop), yet this has changed nothing.

    I can boot into a loopback Ubuntu install on the same drive, which works fine, other than the fact that it has issues with some of the USB ports and the network card.

    This system has worked fine for the past few months, completely stable, and nothing in the configuration has changed before this error started happening.

    Startup Repair on the Windows recovery CD doesn't find any issues.

    Unplugging my secondary hard drive or swapping around memory doesn't change anything.

    The hard drive itself is fine, it hasn't shown any signs of failure and once again, boots my other OS fine.

    If anyone could help with this, that would be great. I can't seem to find any possible solution to this.

    If it makes any difference, my system specs are as follows:

    • AMD FX-8320
    • Gigabyte GA-970A-D3
    • 4GB of DDR3
    • Radeon HD 6870
    • 550w PSU

    I'd like to not have to reinstall Windows, for I have more than a terabyte of data that I would have to back up if that becomes the only option.

    EDIT: I have since tried the following:

    Tried the solution involving restoring files from RegBackup. which changed nothing.

    Tried testing everything with Hiren's boot CD, everything comes back as fine.

    Tried disabling everything unnecessary in the BIOS and unplugging everything unneeded, it still hangs.

    Tried swapping out every possible combination of RAM, it still has the same result. The RAM is not at fault it seems

    Tried every GPU I own (which is many!) and it still hangs at the exact same place.

    Tried minimizing the power consumption as much as possible, even using an old PCI graphics card. It still hangs at the same place in the same way, signifying that it's not the PSU at fault.

    Tried resetting the BIOS again, still nothing.

    Tried every possible combination of BIOS options, even downclocking everything, it still hangs in the same spot.

    Tried upgrading the BIOS from version FB to FD. which changed nothing.

    Based on this, I would conclude the motherboard to be at fault. Are there any other possibilities? I don't want to spend $150 for a new motherboard.

    EDIT 2: This is what it gets stuck at when I try to boot into safe mode:

    Note the slight graphical corruption at the top of the screen. No matter how I set up the system, this seems to be there. In addition, either it has stopped booting into safe mode now, or it takes upwards of 2+ hours, and I haven't left it running for that long.

    How Do I Start Windows in Safe Mode?

    How Do I Start Windows in Safe Mode?

    By Tim Fisher. PC Support Expert

    Tim Fisher is a professional freelance technology author, co-owner of a technology services company for small businesses, and author of Windows 8 Basics in 30 Minutes. published by i30 Media.

    You can read more about Tim's career on his Google+ profile: Tim Fisher .

    Updated March 10, 2015.

    There are lots of reasons you might need to start Windows in Safe Mode and they all involve attempts to solve specific Windows problems.

    When you start your computer in Safe Mode in Windows, you can solve all kinds of problems, especially those involving device drivers and DLL files .

    You may also be able to troubleshoot some Blue Screen of Death errors and other similar issues that interrupt or prevent Windows from starting normally.

    "How Do I Start Windows in Safe Mode?"

    You can start Windows in Safe Mode from either the Startup Settings menu or the Advanced Boot Options menu, depending on which version of Windows you're using.

    Starting Windows in Safe Mode is fairly simple but the exact method differs a little depending on your operating system :

    if you're not sure which of those several versions of Windows is installed on your computer.

    Note: Starting Windows in Safe Mode does not, in and of itself, solve, prevent, or cause any kind of Windows problem. Safe Mode is simply a way of starting Windows with a minimum set of drivers and services in the hopes that the operating system will run correctly.

    Once Windows is in Safe Mode, you can actually perform whatever problem solving steps that might need to be done.

    If you can access Windows normally, you also have the option of configuring Windows to start in Safe Mode automatically the next time your computer starts.

    Start - Start a program

    Start a program, command or batch script (opens in a new window.)

    Always include a TITLE this can be a simple string like "My Script" or just a pair of empty quotes ""

    According to the Microsoft documentation, the title is optional, but depending on the other options chosen you can have problems if it is omitted.

    If command is an internal cmd command or a batch file then the command processor is run with the /K switch to cmd.exe. This means that the window will remain after the command has been run.

    Processor affinity is assigned as a hex number but calculated from the binary positions (similar to NODRIVES )

    Hex Binary Processors

    1 00000001 Proc 1

    3 00000011 Proc 1+2

    7 00000111 Proc 1+2+3

    C 00001100 Proc 3+4 etc

    Document files can be invoked through their file association just by typing the name of the file as a command.

    e.g. START "" MarchReport.DOC will launch the application associated with the .DOC file extension and load the document.

    To minimise any chance of the wrong exectuable being run, specify the full path to command and/or (at a minimum) include the file extension: START notepad.exe

    If you START an application without a file extension (for example WinWord instead of WinWord.exe) then the PATHEXT environment variable will be read to determine which file extensions to search for and in what order. The default value for the PATHEXT variable is. COM;.EXE;.BAT;.CMD

    The SEPARATE and SHARED options are not supported on 64-bit platforms.

    Specifying /NODE allows processes to be created in a way that leverages memory locality on NUMA systems. For example, two processes that communicate with each other heavily through shared memory can be created to share the same preferred NUMA node in order to minimize memory latencies. They allocate memory from the same NUMA node when possible, and they are free to run on processors outside the specified node.

    start /NODE 1 app1.exe

    start /NODE 1 app2.exe

    These two processes can be further constrained to run on specific processors within the same NUMA node.

    In the following example, app1 runs on the low-order two processors of the node, while app2 runs on the next two processors of the node. This example assumes the specified node has at least four logical processors. Note that the node number can be changed to any valid node number for that computer without having to change the affinity mask.

    start /NODE 1 /AFFINITY 0x3 app1.exe

    start /NODE 1 /AFFINITY 0xc app2.exe

    Running executable (.EXE) files

    When a file that contains a .exe header, is invoked from a CMD prompt or batch file (with or without START), it will be opened as an executable file. The filename extension does not have to be .EXE. The file header of executable files start with the 'magic sequence' of ASCII characters 'MZ' (0x4D, 0x5A) The 'MZ' being the initials of Mark Zibowski. a Microsoft employee at the time the file format was designed.

    If Command Extensions are enabled, external command invocation through the command line or the START command changes as follows:

    Non-executable files can be invoked through their file association just by typing the name of the file as a command. (e.g. WORD.DOC would launch the application associated with the .DOC file extension). This is based on the setting in HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.ext\OpenWithList. or if that is not specified, then the file associations - see ASSOC and FTYPE.

    When executing a 32-bit GUI application, CMD.EXE does not wait for the application to terminate before returning to the command prompt. This new behavior does NOT occur if executing within a command script.

    In Windows XP this requires the use of start /wait:

    start /wait /b First.exe

    start /wait /b Second.exe

    When executing a command line whose first token is the string CMD without an extension or path qualifier, then CMD is replaced with the value of the COMSPEC variable. This prevents picking up CMD.EXE from the current directory.

    When executing a command line whose first token does NOT contain an extension, then CMD.EXE uses the value of the COMSPEC environment variable. This prevents picking up CMD.EXE from the current directory.

    When executing a command line whose first token does NOT contain an extension, then CMD.EXE uses the value of the PATHEXT environment variable to determine which extensions to look for and in what order. The default value for the PATHEXT variable is. COM;.EXE;.BAT;.CMD Notice the syntax is the same as the PATH variable, with semicolons separating the different elements.

    When searching for an executable, if there is no match on any extension, then looks to see if the name matches a directory name. If it does, the START command launches the Explorer on that path. If done from the command line, it is the equivalent to doing a CD /D to that path.

    Run a minimised Login script:

    START "My Login Script" /Min Login.cmd

    Start a program and wait for it to complete before continuing:

    START "" /wait autocad.exe

    START \\print_server\printer_name

    Start an application and specify where files will be saved (Working Directory):

    START /D C:\Documents\ /MAX "Maximised Notes" notepad.exe

    START is an internal command.

    “Do not run; scorn running with thy heels”

    Shakespeare, The Merchant of Venice