Обновление Windows 10 KB5001330 приносит очередные проблемы, включая BSOD

В некоторых конфигурациях Windows 10 возникают серьезные проблемы из-за недавнего обновления под номером KB5001330. Пользователи сообщают о проблемах с установкой, проблемах с производительностью, временной ошибке профиля пользователя и предупреждении о сбое системы.

реклама

На этой неделе во вторник Microsoft выпустила новые накопительные обновления за апрель 2021 года для поддерживаемых версий ОС. Для версии 20H2/2004 Microsoft выпустила Windows 10 KB5001330, обязательное обновление безопасности, направленное на устранение ряда уязвимостей и проблем, вызванных предыдущим обновлением, включая проблемы с принтерами.

Согласно многочисленным сообщениям на сайтах социальных сетей, растет число пользователей, которые не могут установить последнее обновление Windows на свое оборудование. При попытке это сделать появляются ошибки: 0x800f081f, 0x800f0984.

Об ошибках при загрузке обновления KB5001330 сообщили многие пользователи в Центре отзывов.

реклама

«Я получаю постоянный сбой при установке KP5001330 с кодом ошибки 0x800f0984. Это происходит на Surface Studio 2 и Pro 7. Второй месяц подряд нельзя установить накопительное обновление на моих устройствах. Установка приостанавливается на 20%, затем снова на 73%, потом на 100%, затем происходит сбой», — отметил один из пользователей.

В редких случаях также может повторяться известная ошибка временного профиля пользователя. Последний раз об этой ошибке сообщалось в декабре, она создает новый профиль пользователя при загрузке операционной системы после применения накопительного обновления. В этом случае пользовательские файлы и настройки (например, обои) могут исчезнуть.

«После обновления я больше не могу войти в свой компьютер. В нем говорится, что службе профилей пользователей не удалось войти в систему. Профиль пользователя не может быть загружен», — пожаловался один пользователь.

«После обновления Windows предлагает войти в гостевой профиль», — другой пользователь подтвердил проблему.

реклама

К счастью, есть обходной путь для решения указанной проблемы. Необходимо либо откатить обновление, либо вручную переместить пользовательские файлы.

Кроме того, пользователи сообщают о сбоях в играх: графических артефактах и значительном падении частоты кадров, но проблему можно решить, удалив накопительное обновление вручную. Лишь некоторые пользователи сообщают об этих проблемах на форумах, и, похоже, они не так распространены, как другие ошибки.

Также многие сталкиваются с периодическими появлениями BSOD (синего экрана смерти)/

«Это обновление сломало Windows для меня и других. BSOD при обновлении сообщал, что определенного драйвера больше нет или он не поддерживается. Я восстановил Windows и обновился снова, затем BSOD на моем ПК повторился дважды за несколько часов. Я удалил обновление. Это случилось не только со мной, поэтому я бы посоветовал не устанавливать это обновление», — сообщил один из пользователей.

реклама

Если вы загрузили обновление April 2021 Patch Tuesday и столкнулись с какими-либо проблемами, лучший способ решить проблему — это удалить исправление, выполнив следующие действия:

1. Откройте приложение «Настройки»;

2. Нажмите «Обновление и безопасность»;

3. Нажмите «Центр обновления Windows»;

4. Нажмите «Просмотреть историю обновлений»;

5. Нажмите «Удалить обновления», затем выберите KB5001330, чтобы удалить его;

6. Перезагрузите компьютер.

На данный момент компания Microsoft никак не прокоментировала многочисленные жалобы пользователей.

Windows Vista

Windows Vista

Windows Vista (codenamed Longhorn) is an operating system by Microsoft, released to manufacturing on 8 November 2006 and general availability on 30 January 2007. It is the seventh operating system in the Windows NT operating system line, succeeding Windows XP and preceding Windows 7. It also had one of the longest development periods in Microsoft’s history starting in May 2001 and continuing until November 2006.

Contents

Development [ edit | edit source ]

The «Longhorn» project started in earnest in May 2001, originally intended as a bridging release between Whistler and the later version of Windows codenamed Blackcomb. As development progressed, many features slated for Blackcomb became part of Longhorn, and employees jumped ship from other parts of the company. As development progressed before the reset, Longhorn became a heavily bloated and unstable piece of vaporware, with release dates being pushed back on several occasions. The first build to leak publicly was build 3683, which contained a new theme and also the foundations for Windows Future Storage (aka WinFS) and Avalon (the codename for the Windows Presentation Foundation (WPF) framework) — the development of which began on or before April 2001 based on dates in the WPF components of the .NET 4.5.1 Reference Source.

Stability increasingly became an issue as development progressed, and very few builds were publicly released as a result. Only two builds were distributed at conferences and to developers: build 4051 and build 4074. The last known confirmed build from before the development reset is build 4093. At 16:29 on 19 August 2004, (the same day as the compilation of 4093), Microsoft reset the development of Windows Longhorn and started fresh using Windows Server 2003 Service Pack 1 as a codebase, starting the Omega-13 period. Immediate post-reset builds were primarily focused on reintegrating features from the pre-reset builds while maintaining stability. Most of these builds are similar to Windows XP in the overall look and feel. Few builds from this stage of development have been released, officially or otherwise. Development of Longhorn continued, albeit many features originally slated for inclusion were delayed or dropped to produce a more realistic set of goals for the OS. Examples of said features include WinFS, «Castle» (later shipped in Windows 7 as HomeGroup) and what would become Windows PowerShell.

In April 2005, a pre-beta build was released to testers (build 5048). This build showed the progress made since the reset and also proved much more stable than previous builds. Build 5112 (Beta 1) was released to the public soon afterward in July and showcased an early version of the Aero interface, as well as many stability improvements over XP. Later that year and the next year, many builds were released to testers in a public beta program, with builds dubbed as «Community Technology Previews» (CTPs). The final build that was pushed out to public preview testers was Release Candidate 2 (build 5744). The RTM build was build 6000.16386, compiled on 8 November 2006.

Main changes [ edit | edit source ]

User interface [ edit | edit source ]

The new Aero user interface has been introduced, which included large design changes to many of the built-in apps. Microsoft also encouraged third party developers to make their applications consistent with Aero, with the company for the first time producing a definite set of design guidelines that included advice ranging from graphics design to message text wording.

An important aspect of the user interface was the hardware accelerated Windows Aero theme. This was made possible by the new Desktop Window Manager, a compositing window manager that worked hand in hand with the also new Windows Display Driver Model (WDDM). The compositing nature of DWM allows for eye candy such as Aero Glass or Flip 3D, but also prevents various rendering glitches that were common for previous versions of Windows. The exact appearance of Aero Glass can be further customized by toggling the transparency or changing the frame’s color, which is not possible for themes that are not composited.

For systems that relied on older drivers made for Windows XP, Vista also included the Windows Basic style, which used the older XP-style theme engine.

Editions [ edit | edit source ]

Windows Vista came in many editions. Unlike Windows XP, there was no special edition for Media Center and 64-bit capability, since these features were included in at least one of the consumer editions. Windows Vista also did not have an embedded version, perhaps due to the considerable grunt required to run optimally.

• Starter: This edition is intended for emerging markets and low-cost PCs. As in XP, the three-program limit was there, and only 1GB RAM was accepted. Other software restrictions applied as well. This version is hence not available in 64-bit.
• Home Basic: Found in low cost to mid-end, this version of Windows Vista does not fully have Aero (though it has DWM) and hence does not have effects like transparency and 3D Flip. Windows Media Center is also not present in this edition. Parental Controls are included, however. Unlike the Starter edition, it does not have the hardware and 3-program limit.
• Home Premium: The consumer version of Windows Vista, this version includes full Aero functionality and Windows Media Center. It also includes Premium Games (eg — InkBall).
• Business: The business-oriented version of Windows Vista, it contains several features like full RDP (client/host) capability, Group Policy, and domain joinability. However, Windows Media Center and Parental Controls are not included, and Premium Games are disabled by default.
• Ultimate: The top consumer variant of Windows Vista, it is a merger of the features included Windows Vista Home Premium and Business. BitLocker is included in this version.
• Enterprise: The business variant of Windows Vista. It is similar to Ultimate, but without Windows Media Center and includes enterprise-specific tools.

Myths and legends [ edit | edit source ]

Sound scheme [ edit | edit source ]

No build of Windows Vista (including pre-reset) used or even included the widespread sound scheme that appears in several fanmade Longhorn or Vista themes, which was actually a sound scheme titled «Deep Fantasy», commercially available on NEO Sounds, a stock sound/music website in the 2000s. The Windows XP sounds remain and are used in all pre-reset builds, with a few being swapped with Vista sounds between builds 5469 and 5840.16384.

Microsoft windows was 5048

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I am currently managing a Windows Server 2012 box running several sites in IIS. At least twice a week, completely at random, my sites have been going offline. After reviewing the server logs I find that the following event is firing every time these sites go down.

Microsoft-Windows-WAS — 5186 — A worker process with process id of ‘XXXX‘ serving application pool ‘XXXXX‘ was shutdown due to inactivity. Application Pool timeout configuration was set to 90 minutes. A new worker process will be started when needed.

It appears that these events are fired for each site that I am currently hosting. For some reason, when this happens, it appears that the application pools never restart as the site remains completely offline.

I have tried increasing the Idle Time-out from 90 minutes to 12 hours (720 minutes), unfortunately, some of these sites do not have interaction on a daily basis. Any help would be greatly appreciated here!

Windows Vista build 5048

Version of Microsoft Windows
OS family	Windows NT
Version	6.0
Codename	Longhorn
Preliminary name
Architecture	x86, x64
Latest build
Release date	2007-01-30
Support end	2017-04-11
Server counterpart
Windows Server 2008
Replaces
Windows XP
Replaced by
Windows 7

6.0.5048.winmain_idx02.050401-0536

Build of Windows Vista
OS family
Architecture	x86, x64
Compiled	2005-04-01
Timebomb	2005-09-28 (+180 days)
Works in
About
SKUs
Professional
Key
TCP8W-T8PQJ-WWRRH-QH76C-99FBW
Windows Vista build 5048 is a pre-Beta 1 build of Windows Vista. This build was released to attendants of WinHEC 2005 on 24 April 2005, and it was officially known as the «Longhorn Developer Preview». Being a pre-beta 1 build, it is noticeably closer to Windows XP and Windows Server 2003 than to pre-reset builds. It is also an idx02 build, which suggest that it was recompiled several times, and therefore is behind regular builds compiled at the time. The x64 version of this build is similar to the x86 build, but it has a different EULA and Windows XP x64 Edition brand wallpaper instead of the Windows Server 2003 brand wallpaper which is named as winxp.jpg . Unlike other post-reset Vista builds, it was compiled in evaluation mode, and it can be installed on the current date. The timebomb in evaluation mode behaves just like pre-reset builds; if the timebomb expires, the user is automatically logged out. Contents Setup [ edit | edit source ] Although previous builds of post-reset Vista re-used the older i386 installation process, this build re-uses the Windows Preinstallation Environment installation process from later builds of Longhorn, retaining the slate theme as well. However, a few changes have been made. The launching WinPE screen does not show anymore, now leaving you without any option of pressing F6 to load in certain drivers. The starting setup screen has also been majorly uplifted, now containing the Windows flag. Anti-aliasing is no longer present on fonts, and the numbers on the progress bar no longer glow. Finally, the hardware portion of setup now includes a dummy progress bar on the bottom (all it does is just continuously increase in size until it reaches the end, then it goes back to the start), and the Windows flag has been added to the middle of the page. Asides from all of these minor changes, setup is overall mostly similar to what was found in later pre-reset builds of Longhorn. The setup autorun is notable for containing a mention of Beta 1, in this case the second button is labeled View Beta 1 Release notes. Setup — review and adjust changes Setup — disk partitioning Setup — warning upon disk partitioning Setup — computer name Setup — copying files Setup — hardware portion New features and changes [ edit | edit source ] This build includes Windows System Assessment Tool (shortly WinSAT) and Windows Diagnostic Infrastructure (WDI). The Jade and Slate themes are no longer included. Windows Media Player 10 and Internet Explorer 6 SP2 are also now present. Sync Manager (Later known as Sync Center) has been introduced. Many of the icons from later pre-reset builds have returned, albeit with minor alterations. A few icons are also new to this build. However, the Control Panel and Printers icons are from Windows 95. This build uses the old way of logging in (the one seen in Windows 2000) by default. The ‘new’ login screen can be enabled in the control panel, but it is just an exact replica of Windows XP’s login screen. This build uses BOOTMGR as the default bootloader, but still includes NTLDR as an alternative way to boot. This can be seen via a dual boot. As a result, this build also contains the notable red screen (RSOD) when a boot error occurs. This build is the first to not boot without ACPI, since it results in an error. You can choose a bunch of different themes, including the Windows XP Luna themes, the classic theme, and the three new Aero themes. Paint received an update which added a zoom slider to the app (it was readded from Windows Longhorn build 4051). Self-Healing NTFS was reintegrated from Windows Longhorn build 4074. Instant Search was implemented in this build. Control Panel’s Category View was revamped and applets were added for installed programs. Search UI was updated to manage search criteria specifications. Microsoft Anna Speech Synthesizer from build 4093 was added. However, it is slightly different. Advanced Options has a blue background, rather than black seen in RTM. Start Menu [ edit | edit source ] Start Menu received many new updates in this build including the famous search box that will later be seen in Windows Vista and Windows 7, and the outlining of the start menu being transparent. «All Programs» menu is now an inline menu and it doesn’t open in a separate context menu-like UI. Customize Start Menu has references to «My Games» and «My Hardware» links. Aero [ edit | edit source ] This build makes the debut of the Aero theme, by default it is loaded without DWM. This build includes three new Aero themes. One of the new Aero themes (Theme 2) use a similar design to later builds of Vista (The only difference is that the minimize and maximize buttons are little arrows, minimize arrow points down and maximize arrow points up, but other than that, its basically the same.) Aero theme is now the default theme overall system, along with its visual effects and wizards. Desktop Window Manager [ edit | edit source ] This build of Vista readds the Desktop Window Manager, after being absent in builds 4083-4093 (including Omega-13 builds 3790, 5000 (with multiple compiles) and 5001). This build includes Desktop Window Manager, but it can crash at startup if no driver is installed, in which case software emulation is needed if no driver is available. LDDM drivers are now included by default, supporting many (but not all) GPUs of the time, however the DWM can run with a regular XPDM driver, using a registry edit. There are two different ways of initializing DWM, one by modifying the registry, while the other being initializing a DLL via rundll32.exe. The more simpler rundll32.exe method is simply opening up the command prompt, and typing rundll32 udwm.dll,DwmClientStartup . This, however, randomizes the effects used with DWM. The other method of initializing DWM can be done via opening the Registry Editor, navigating to HKEY_LOCAL_MACHINE/Software/Microsoft , creating a new key called DWM, then creating the following 3 DWORDs inside the key: Key Values EnableMachineCheck 1 — enabling machine check, which disallows the possibility of using XPDM drivers 0 — disables machine check ForceSoftwareD3D 1 — forces software rendering 0 — hardware rendering Metal 1 — makes the titlebar yield an opaque a metal-like style 0 — transparent titlebars UseAlternateButtons 1— square-like buttons any other value — smaller Vista-like buttons Once making the following changes, simply log out of the system, then log back in. User Account Control [ edit | edit source ] This build includes User Account Control (A prototype version of this feature can be first seen in Windows Longhorn build 4031) Bugs and quirks [ edit | edit source ] The setup switches to 16-bit color 800×600 video mode after briefly using 24-bit 640×480 during its startup, resulting in a noticeable dithering effect of the background during setup. There is a limit of 50 files able to be browsed per folder, but it can be bypassed by viewing icons in groups. Enabling auto login for the default user account while having the new login screen enabled can make the login screen throw up an error. This can be safely ignored. Help and Support does not open due to a missing helpctr.exe , but an updated help application, called HelpPane.exe , can be found in the Windows folder. Although this build can partition properly during setup, the partitioning page doesn’t refresh properly, requiring you to reboot your system in order to see the new partition. Upgrading [ edit | edit source ] While this build requires build 5019 or higher to upgrade to, preupgradenotice.txt in the sources folder lists various bugs that will be encountered when an upgrade takes place. File differences [ edit | edit source ] The following files have been introduced, renamed or removed from build 5001: Added files Name Description Version Bliss.jpg bootmgr Longhorn.jpg wmstream.dll Windows Media Streamer DLL 8.0.0.4487 wmv8ds32.ax wmvadvd.dll Windows Media Video 9 Decoder 10.0.0.3646 wmvadve.dll Windows Media Video 9 Decoder 10.0.0.3646 WMVDECOD.DLL Windows Media Video Decoder 10.0.0.961 WMVENCOD.DLL Windows Media Video 9 Encoder 10.0.0.961 WMVSDECD.DLL Windows Media Screen Decoder 10.0.0.961 WMVSENCD.DLL Windows Media Screen Encoder 10.0.0.260 WMVXENCD.DLL Windows Media Video Encoder 10.0.0.961 wpdconns.dll WPD Connection Objects 5.2.3790.3658 wpdmtp.dll 5.2.3790.3658 wpdmtpdr.dll 5.2.3790.3658 wpdmtpus.dll Usbscan transport layer for MTP driver 5.2.3790.3658 wpdtrace.dll WPD Tracing 5.2.3790.3658 wscmisetup.dll Installers for Winsock Transport and Name Space Providers 6.0.5048.0 wscntfy.dll wscsvc.dll wscui.cpl WSDApi.dll Web Services for Devices API DLL 6.0.5048.0 wshBth.dll Windows Sockets Helper DLL wshirda.dll Windows Sockets Helper DLL 6.0.5048.0 WUDFCoinstaller.dll Windows Driver Foundation — User-mode Platform Device Co-Installer 6.0.5048.0 WUDFHost.exe Windows Driver Foundation — User-mode Driver Framework Host Process 6.0.5048.0 WUDFPlatform.dll Windows Driver Foundation — User-mode Platform Library 6.0.5048.0 WUDFSvc.dll Windows Driver Foundation — User-mode Driver Framework Services 6.0.5048.0 WUDFx.dll wups2.dll Windows Update client proxy stub 2 wvc.dll xmlrw.dll Microsoft XML Slim Library 2.00.3526.0 Renamed files Old filename New filename Old description New description Version Moon flower.jpg Moon.jpg Purple flower.jpg PurpleF.jpg Red moon desert.jpg RedMoon.jpg Stonehenge.jpg StoneH.jpg Vortec space.jpg Vortec.jpg Windows XP.jpg winxp.jpg Removed files Name Description Version wmvdmod.dll Windows Media Video Decoder 10.0.0.3646 wmvdmoe2.dll Windows Media Video Encoder 10.0.0.3646 wmvds32.ax wowfax.dll Windows 3.1 Compatible Fax Driver DLL 0.2.0.0 wowfaxui.dll wshatm.dll Windows Sockets Helper DLL 6.0.5001.0 wshisn.dll NWLINK2 Socket Helper DLL 6.0.5001.0 wstdecod.dll wuauclt1.exe wuaueng1.dll Gallery [ edit | edit source ] Error when trying to install without ACPI Boot error (this error relates to non-compliant ACPI BIOS) Читайте также:  Linux installed package version Оцените статью Вам также может понравиться Windows или Linux: Что лучше выбрать? Есть много причин выбирать между Windows и Linux, но Файл владелец изменить linux Команда Chown в Linux Chown Command in Linux (File Установка шлюза по умолчанию linux Настройка сети вручную Содержание Краткое описание Чем разбить диск для linux ИТ База знаний Курс по Asterisk Полезно — Узнать IP — Правообладателям Политика конфиденциальности Контакты