Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
ex-iskon-pleme :: Lifestyle :: IT
Page 1 of 1
Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
[size=36]Microsoft releases Windows 10 builds 16299.192, 15063.850 - here's what's new[/size]
By Rich Woods @@TheRichWoods · Jan 4, 2018 · HOT!23
Today, a security vulnerability was found that affects pretty much every PC on the market. Chips from Intel, AMD, and ARM are affected, as are Windows, macOS, and Linux, on the software end. macOS and Linux have already been patched, and Microsoft planned to update Windows on Tuesday, but then the news broke, and it was time to release some emergency updates.
If you're on the Fall Creators Update, or version 1709, you're going to see KB4056892, or build 16299.192. It can be manually downloaded here, and contains the following fixes:
The rest of the updates contain smaller changelogs. If you're on the Creators Update, or version 1703, you'll see KB4056891, or build 15063.850, which can be manually downloaded here. This one really only contains the security fixes:
Those on the Anniversary Update, or version 1607, will get KB4056890, or build 14393.2007, and those on version 1511 will get KB4056888, or build 10586.1356. They can be manually downloaded here and here, respectively, and contain the same changelogs as build 15063.850.
As for the original version of Windows 10, now called version 1507, it can be manually downloaded here and contains the following fixes:
Naturally, you don't need to download any of them manually. You can go to Settings -> Update & security -> Windows Update -> Check for updates, and you'll automatically get the ones for your version of Windows 10. You'll also need some firmware updates before you're completely protected from today's security issue.
PREVIOUS STORY
By Rich Woods @@TheRichWoods · Jan 4, 2018 · HOT!23
Today, a security vulnerability was found that affects pretty much every PC on the market. Chips from Intel, AMD, and ARM are affected, as are Windows, macOS, and Linux, on the software end. macOS and Linux have already been patched, and Microsoft planned to update Windows on Tuesday, but then the news broke, and it was time to release some emergency updates.
If you're on the Fall Creators Update, or version 1709, you're going to see KB4056892, or build 16299.192. It can be manually downloaded here, and contains the following fixes:
It also contains some known issues to be aware of:
- Addresses issue where event logs stop receiving events when a maximum file size policy is applied to the channel.
- Addresses issue where printing an Office Online document in Microsoft Edge fails.
- Addresses issue where the touch keyboard doesn’t support the standard layout for 109 keyboards.
- Addresses video playback issues in applications such as Microsoft Edge that affect some devices when playing back video on a monitor and a secondary, duplicated display.
- Addresses issue where Microsoft Edge stops responding for up to 3 seconds while displaying content from a software rendering path.
- Addresses issue where only 4 TB of memory is shown as available in Task Manager in Windows Server version 1709 when more memory is actually installed, configured, and available.
- Security updates to Windows SMB Server, the Windows Subsystem for Linux, Windows Kernel, Windows Datacenter Networking, Windows Graphics, Microsoft Edge, Internet Explorer, and the Microsoft Scripting Engine.
Update installation may stop at 99% and may show elevated CPU or disk utilization if a device was reset using the Reset this PC functionality after installing KB4054022. | Note: This workaround uses c:\temp and the x64 architecture as examples. Update these examples as appropriate for your environment. [list="box-sizing: border-box; outline: none; margin-right: 0px; margin-bottom: 26px; margin-left: 0px; padding-right: 0px; padding-left: 40px; vertical-align: baseline; font-style: inherit; font-variant: inherit; font-weight: inherit; font-stretch: inherit; line-height: inherit; font-family: inherit; border: 0px; list-style-position: initial; list-style-image: initial;"] [*]Download the appropriate version of KB4054022 for your device architecture from the Microsoft Update Catalog to c:\temp. Then run the commands in the steps below from the administrative command prompt. [*]Expand the .msu file that you downloaded in step mkdir c:\temp expand -f:* windows10.0-kb4054022-x64.msu c:\temp [*]End the existing TrustedInstaller processes and install KB4054022 using the Deployment Image Servicing and Management tool. taskkill /f /im tiworker.exe taskkill /f /im trustedinstaller.exe dism /online /add-package /packagepath:c:\temp\Windows10.0-KB4054022-x64.cab [*](Optional) Delete the CBS logs from the Windows Logs directory. del /f %windir%\logs\cbs\*.log [/list] Microsoft is working on a resolution and will provide an update in an upcoming release. |
Windows Update History reports that KB4054517 failed to install because of Error 0x80070643. | Even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. To verify the installation, select Check for Updates to confirm that there are no additional updates available. You can also type About your PC in the Search box on your taskbar to confirm that your device is using OS Build 16299.125. Microsoft is working on a resolution and will provide an update in an upcoming release. |
When calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions. | Microsoft is working on a resolution and will provide an update in an upcoming release. |
Due to an issue with some versions of Anti-Virus software, this fix is only being made applicable to the machines where the Anti virus ISV has updated the ALLOW REGKEY. | Contact your Anti-Virus AV to confirm that their software is compatible and have set the following REGKEY on the machine Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000” |
The rest of the updates contain smaller changelogs. If you're on the Creators Update, or version 1703, you'll see KB4056891, or build 15063.850, which can be manually downloaded here. This one really only contains the security fixes:
There are also a couple of known issues:
- Security updates to Internet Explorer, Microsoft Scripting Engine, Microsoft Edge, Windows Graphics, Windows Kernel, Windows Subsystem for Linux, and the Windows SMB Server.
When calling CoInitializeSecurity, the call will fail if passing RPC_C_IMP_LEVEL_NONE under certain conditions. | Microsoft is working on a resolution and will provide an update in an upcoming release. |
Due to an issue with some versions of Anti-Virus software, this fix is only being made applicable to the machines where the Anti virus ISV has updated the ALLOW REGKEY. | Contact your Anti-Virus AV to confirm that their software is compatible and have set the following REGKEY on the machine Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat" Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc" Type="REG_DWORD” Data="0x00000000” |
Those on the Anniversary Update, or version 1607, will get KB4056890, or build 14393.2007, and those on version 1511 will get KB4056888, or build 10586.1356. They can be manually downloaded here and here, respectively, and contain the same changelogs as build 15063.850.
As for the original version of Windows 10, now called version 1507, it can be manually downloaded here and contains the following fixes:
It contains the same two known issues as the other older versions of the OS.
- Addresses issue where using smart cards on a Windows Terminal Server system may cause excessive memory usage.
- Security updates to Internet Explorer, Microsoft Scripting Engine, Microsoft Edge, Windows Graphics, Windows Kernel, Windows Datacenter Networking, and Windows SMB Server.
Naturally, you don't need to download any of them manually. You can go to Settings -> Update & security -> Windows Update -> Check for updates, and you'll automatically get the ones for your version of Windows 10. You'll also need some firmware updates before you're completely protected from today's security issue.
- MICROSOFT
- WINDOWS 10
- BUILD 16299.192
- BUILD 15063.850
- BUILD 14393.2007
- BUILD 10586.1356
- BUILD 10240.17738
PREVIOUS STORY
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
[size=36]Microsoft adds six known issues to Windows 10 build 17063[/size]
By Rich Woods @@TheRichWoods · Jan 4, 20189
Windows 10 Insider Preview build 17063 really is the gift that keeps on giving. Originally released on December 19 with a ton of new features, Microsoft added three known issues three days later. It would seem as though Insiders filed a lot of bugs over the holiday break though, as yet another six known issues were added today.
If you're still thinking about installing build 17063, you'll want to be aware of the following:
One thing that isn't a known issue in build 17063 is the security flaw that was found recently in just about all chipsets and operating systems, now called Spectre and Meltdown. This was already fixed in the most recent builds, so Insiders were protected by the time it was announced.
By Rich Woods @@TheRichWoods · Jan 4, 20189
Windows 10 Insider Preview build 17063 really is the gift that keeps on giving. Originally released on December 19 with a ton of new features, Microsoft added three known issues three days later. It would seem as though Insiders filed a lot of bugs over the holiday break though, as yet another six known issues were added today.
If you're still thinking about installing build 17063, you'll want to be aware of the following:
Obviously, these issues may be impactful for you, and you might want to just wait for the next build to hit the Fast ring. Insider chief Dona Sarkar has confirmed, however, that there won't be any new builds this week, so we can hope for next week.
- Some PCs will bugcheck (GSOD) when entering into Connected Standby.
- When you open Task View immediately after an upgrade, Timeline may not be visible. If you encounter this, wait 15-30min and try launching Task View again.
- We’re investigating an issue where some Bluetooth devices don’t work on this build and Device Manager shows error 43 for these drivers.
- The Settings app may crash on certain pages if the Settings window isn’t big enough. Windows Update Settings is one of the pages impacted. If you’re experiencing this, maximizing the Settings window (so it’s full screen) will resolve it.
- In certain cases, USB devices with unreliable connections may cause bugchecks (GSOD) on PCs.
- Attention developers: Build 17063 has an issue running Linux containers with Docker Community Edition for Windows (edge) on many machines. The docker pull or docker run commands will fail with an error “Not enough memory resources are available to complete this operation”. We’re working on a fix for an upcoming Windows Insider build but you can work around the problem now with these steps:
[list="box-sizing: border-box; outline: none; margin-right: 0px; margin-bottom: 26px; margin-left: 0px; padding-right: 0px; padding-left: 40px; vertical-align: baseline; font-style: inherit; font-variant: inherit; font-weight: inherit; font-stretch: inherit; line-height: inherit; font-family: inherit; border: 0px; list-style-position: initial; list-style-image: initial;"]- Be sure “Docker for Windows” is running, then right-click the whale icon in the notification area and choose “settings”.
- On the General tab, uncheck “Enable Linux containers on Windows”.
- Next a dialog “Switch to Standard mode (Linux VM / Windows daemon” will pop up. Click OK.
- Wait for the whale icon to turn white.
[/list]
One thing that isn't a known issue in build 17063 is the security flaw that was found recently in just about all chipsets and operating systems, now called Spectre and Meltdown. This was already fixed in the most recent builds, so Insiders were protected by the time it was announced.
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
https://www.neowin.net/news/microsoft-adds-six-known-issues-to-windows-10-build-17063?utm_referrer=https%3A%2F%2Fzen.yandex.com
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
objasni u par rečenica da nečitam sve ovo
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
Win.10 je toliko sranje da je poprimilo fizički oblik, sranje i krađa ja ne znam kako se može prodavati tako što?
Kermit-
Posts : 26479
2014-04-17
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
boli me krc za windovze, imam na virtualno mashini winse7 i ok su, ostalo odradjuje brat linux
_________________
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
Ne znam,nisam čito..ugl,navodno je MS neasaosoftwaresko rjesenje za uklanjanje bug,onog sa drugew teme..Pinochet wrote:objasni u par rečenica da nečitam sve ovo
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
asilovski wrote:Win.10 je toliko sranje da je poprimilo fizički oblik, sranje i krađa ja ne znam kako se može prodavati tako što?
st obi rekao da sve vise kompova,bar je slucaj u HP-a,da se nISTA DRUGO NITI NE MOZE INSTALIRATI;SAMO WIN10?
sestra kupila neki drek HP-ov za 240 Ojra..ono klinika nabavljala a ona onako se zgrecala za jedan,bez merverštojera,a Boga mi,toliko i vrijedi..
instalirao Ubuntu paraleno,jerbo je rekla da je WIN 10 konfuzan,i Ubuntu je pretrpio dva BOOT-a dok nije se zledio,i nit makac..
Probam na lajf dici sa LinuxMintom,odmah ga u startu sledi..neki Vačdog,neki sustav hardwera,koji kontrolira da nis osim W10 ne sjedne na lap..
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
[size=36]Intel responds to security vulnerability, calling out AMD and ARM[/size]
By Rich Woods @@TheRichWoods · Jan 3, 2018 · HOT!26
Earlier today, it was reported that there's a major security vulnerability in all modern Intel chips that can provide kernel access to an attacker. Intel has now responded to the issue, saying that it's not exclusive to its products, specifically calling out AMD and ARM Holdings as companies that it's working with to fix the exploit.
Tom Lendacky, a software engineer from AMD, has stated that the company's processors aren't affected at all. Of course, Intel didn't specifically say that AMD chips are vulnerable, but we've reached out to the company for a statement.
Intel also took issue with reports that fixes will cause performance issues. The firm said that any performance impact will be "workload-dependent", and that the average consumer won't even notice it. The effect will also be lessened over the course of future updates.
It seems likely that we'll find out more about this next week on Patch Tuesday, and other companies like AMD and Qualcomm are likely to chime in as well.
By Rich Woods @@TheRichWoods · Jan 3, 2018 · HOT!26
Earlier today, it was reported that there's a major security vulnerability in all modern Intel chips that can provide kernel access to an attacker. Intel has now responded to the issue, saying that it's not exclusive to its products, specifically calling out AMD and ARM Holdings as companies that it's working with to fix the exploit.
While Intel only called out AMD and ARM Holdings by name, it also said that it's working with "several operating system vendors". These operating systems should include Windows, Linux, and macOS, and while macOS and Linux have been patched, Windows should get updates across the board next Tuesday. Intel said that it was planning to announce the vulnerability then.Recent reports that these exploits are caused by a “bug” or a “flaw” and are unique to Intel products are incorrect. Based on the analysis to date, many types of computing devices — with many different vendors’ processors and operating systems — are susceptible to these exploits.
Tom Lendacky, a software engineer from AMD, has stated that the company's processors aren't affected at all. Of course, Intel didn't specifically say that AMD chips are vulnerable, but we've reached out to the company for a statement.
Intel also took issue with reports that fixes will cause performance issues. The firm said that any performance impact will be "workload-dependent", and that the average consumer won't even notice it. The effect will also be lessened over the course of future updates.
It seems likely that we'll find out more about this next week on Patch Tuesday, and other companies like AMD and Qualcomm are likely to chime in as well.
Guest- Guest
Re: Mikrosoft rilis Vindovs 10 builds ..i neke brojke,ugl,nvd ispravlja onai bag..
Microsoft patches Windows to cool off Intel's Meltdown – wait, antivirus? Slow your roll
The Redmond giant issued the out-of-band update late yesterday for Windows 10 version 1709.
While the documentation for the fix does not name Chipzilla's CPU-level vulnerability specifically, a Microsoft spokesman told El Reg it will hopefully protect Windows users from Meltdown exploits, and more patches are in the works. Meltdown is a design flaw in Intel's processors going back at least 2011 that allows normal user programs to read passwords, keys and other secrets from the operating system's protected kernel memory area. To prevent this from happening, the kernel has to be moved into a separate virtual address space from user processes.
The software giant is also deploying updates to its Azure cloud service to protect customers from attack. AMD processors are not affected by Meltdown.
Before rushing to install the patch, however, users and admins should note one important issue: the fix may not yet be compatible with your antivirus software.
Microsoft noted that, unless a registry key is updated by the antivirus package, installing the security patch can result in a blue screen of death (BSoD). For that reason, Microsoft said it has set the update to only apply when the registry key has been changed. In other words, antivirus tools must set the key when they are confirmed to be compatible with the operating system update. The patch introduces a significant change to the design of Windows' internal memory management, and this is probably tripping up anti-malware tools, which dig into and rely on low levels of the system.
Some AV vendors have already issued updates to change the key, and allow the fix to be applied without causing any cockups, while others have an update in the works to be released this week or early next week. The malware hunters expected the Windows patches to be released next week, and were caught out when Microsoft brought its patches forward after Meltdown exploit code emerged on the web.
Vendors reported to have updates are Symantec, F-Secure, Avast, and Microsoft's own Windows Defender platform. Check that link for a table of supported and not supported products – obviously, if there is no support, don't flip the key.
Users and admins who are comfortable editing Registry keys themselves can manually perform the task by setting the following:
Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
Data="0x00000000”
Also, people installing the Windows Server patches should ensure they are enabled, too. They are disabled by default due to the potential performance hit involved. Casual desktop users and gamers shouldn't notice any difference, although servers running non-CPU-bound intensive workloads – such as anything that hammers disk storage, the network or just makes a lot of system calls – will suffer to some degree with the Meltdown patch applied. Your mileage may vary.
Elsewhere, Red Hat said it has also kicked out a patch for all three of the CVE listings (CVE-2017-5754, CVE-2017-5753, CVE-2017-5715) associated with the Spectre and Meltdown bugs. The vendor notes that the patch applies to versions of the kernel in releases as far back as RHEL 5. Red Hat's OpenStack and Virtualization releases will also get the fix. Check with your favorite Linux distro for similar updates. Apple quietly patched the Meltdown bug in macOS, and in iOS on its iThings, in December.
Check your anti-malware tool unless you like BSoDs
By Shaun Nichols in San Francisco 4 Jan 2018 at 21:09
89 SHARE ▼A real meltdown ... Vehicle graveyard at the Chernobyl nuclear disaster site (Credit: Roberts Vicups)
Microsoft has released updates for Windows to block attempts by hackers and malware to exploit the Meltdown vulnerability in Intel x86-64 processors – but you will want to check your antivirus software before applying the fixes.The Redmond giant issued the out-of-band update late yesterday for Windows 10 version 1709.
While the documentation for the fix does not name Chipzilla's CPU-level vulnerability specifically, a Microsoft spokesman told El Reg it will hopefully protect Windows users from Meltdown exploits, and more patches are in the works. Meltdown is a design flaw in Intel's processors going back at least 2011 that allows normal user programs to read passwords, keys and other secrets from the operating system's protected kernel memory area. To prevent this from happening, the kernel has to be moved into a separate virtual address space from user processes.
The software giant is also deploying updates to its Azure cloud service to protect customers from attack. AMD processors are not affected by Meltdown.
Before rushing to install the patch, however, users and admins should note one important issue: the fix may not yet be compatible with your antivirus software.
Microsoft noted that, unless a registry key is updated by the antivirus package, installing the security patch can result in a blue screen of death (BSoD). For that reason, Microsoft said it has set the update to only apply when the registry key has been changed. In other words, antivirus tools must set the key when they are confirmed to be compatible with the operating system update. The patch introduces a significant change to the design of Windows' internal memory management, and this is probably tripping up anti-malware tools, which dig into and rely on low levels of the system.
Some AV vendors have already issued updates to change the key, and allow the fix to be applied without causing any cockups, while others have an update in the works to be released this week or early next week. The malware hunters expected the Windows patches to be released next week, and were caught out when Microsoft brought its patches forward after Meltdown exploit code emerged on the web.
Vendors reported to have updates are Symantec, F-Secure, Avast, and Microsoft's own Windows Defender platform. Check that link for a table of supported and not supported products – obviously, if there is no support, don't flip the key.
Users and admins who are comfortable editing Registry keys themselves can manually perform the task by setting the following:
Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"
Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"
Type="REG_DWORD”
Data="0x00000000”
Also, people installing the Windows Server patches should ensure they are enabled, too. They are disabled by default due to the potential performance hit involved. Casual desktop users and gamers shouldn't notice any difference, although servers running non-CPU-bound intensive workloads – such as anything that hammers disk storage, the network or just makes a lot of system calls – will suffer to some degree with the Meltdown patch applied. Your mileage may vary.
Elsewhere, Red Hat said it has also kicked out a patch for all three of the CVE listings (CVE-2017-5754, CVE-2017-5753, CVE-2017-5715) associated with the Spectre and Meltdown bugs. The vendor notes that the patch applies to versions of the kernel in releases as far back as RHEL 5. Red Hat's OpenStack and Virtualization releases will also get the fix. Check with your favorite Linux distro for similar updates. Apple quietly patched the Meltdown bug in macOS, and in iOS on its iThings, in December.
Guest- Guest
Similar topics
» Zoki neke su zene borbene neke glume
» Neke ćemo da povučemo(za uši) a neke ćemo i da oteramo.
» Delegacija SAD "ispravlja brljotine"
» Gde se ispravlja pravopis, ponavlja mi reci non stop
» Donald Tramp ispravlja nepravdu prema Srbiji
» Neke ćemo da povučemo(za uši) a neke ćemo i da oteramo.
» Delegacija SAD "ispravlja brljotine"
» Gde se ispravlja pravopis, ponavlja mi reci non stop
» Donald Tramp ispravlja nepravdu prema Srbiji
ex-iskon-pleme :: Lifestyle :: IT
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum