Jump to content

Search the Community

Showing results for tags '1709'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 5 results

  1. Microsoft is extending support for Windows 10 version 1709 for six months It's been nearly a year since support ended for Windows 10 version 1709 on Home and Pro SKUs. But while consumer versions of Windows 10 are supported for 18 months, some Enterprise and Education SKUs - including updates released in the fall and anything before version 1903 - get 30 months. The Windows 10 Fall Creators Update was set to be retired completely on April 14, but with the end of life imminent, Microsoft is extending support for six months. This is due to the impact that the COVID-19 coronavirus is already having on businesses, and an attempt to not make it harder on them. The new end of life date for Windows 10 Enterprise, Education, and IoT Enterprise will be October 13 for version 1709. In the blog post, Microsoft also suggested that organizations adopt Windows Update for Business, which will allow them to get updates faster. With this extension of support, it's worth noting that support for version 1803 ends just a month later. And since version 1903 uses the new 18-month timeframe for spring updates, that ends just a month after that in December. Source: Microsoft is extending support for Windows 10 version 1709 for six months (Neowin)
  2. After next week, Microsoft will no longer issue updates for Windows 10 version 1607 Enterprise and Education editions or Windows 10 version 1709 Home and Pro editions. Microsoft / Thinkstock End-of-support deadlines for a pair of Windows 10 feature upgrades will soon come into play, halting all updates, including security fixes, to affected devices. The final updates for Windows 10 Enterprise 1607, Windows 10 Education 1607, Windows 10 Home 1709 and Windows 10 Pro 1709 will be issued a week from today, on April 9, according to Microsoft's definitive patch calendar. Microsoft tags its feature upgrades with yymm labels that mark their purported completion dates, even though they typically reach users in a later month. Windows 10 1607, for example, began delivery Aug. 2, 2016 (not in July, as the mm half stated), and 1709 debuted Oct. 17, 2017 (not in September). Customers running Windows 10 Enterprise 1607 or Windows 10 Education 1607 will have had 32 months of support by the time the SKU (stock-keeping unit) rides into retirement. That extra-long support lifecycle came about because of a pair of extensions Microsoft gave to that upgrade, and others, last year. Originally slated to receive 20 months of patches, 1607 was first stretched to 26 months, then to 32. Users powering their PCs with Windows 10 Home 1607 or Windows 10 Pro 1607 were given their final updates a year ago, on April 10, 2018. Only devices with Enterprise or Education were handed the longer support period. Meanwhile, next Tuesday will also see the last updates delivered to personal computers and tablets running Windows 10 Home 1709 and Windows 10 Pro 1709. Those SKUs were allocated the now-standard 18 months of support. Windows 10 Enterprise 1709 and Windows 10 Education 1709, however, have an additional 12 months of updates due them, as those feature upgrades were among several which were "grandfathered" into the longer 30-month lifecycle when Microsoft last rewrote its support policies. (Yes, this is confusing as all get out. No, Computerworld doesn't know whether Microsoft does this on purpose.) Devices operating under the control of Windows 10 Home 1709, Windows 10 Pro 1709, Windows 10 Enterprise 1607 or Windows 10 Education 1607 need to upgrade to a later version to continue to receive security and non-security bug fixes. The next Windows 10 support deadline will be Oct. 8, 2019, when Enterprise 1703 and Education 1703 will receive their final updates. IDG Microsoft's support lifecycle stop dates for two feature upgrades, Windows 10 Enterprise/Education 1607 and Windows 10 Home/Pro 1709, arrive in just one week. Source: End of support looms for Windows 10 versions 1607 and 1709 (Computerworld - Gregg Keizer))
  3. The February patch for Windows 10 Fall Creators Update, version 1709, has drawn criticism and problem reports of many shades, from many corners. Thinkstock/Microsoft At least it isn’t as bad as last month’s three cumulative updates for the bestest version of Windows 10 — on Jan. 3, Jan. 18, and Jan. 31 — but many people running the latest version of Windows 10, version 1709, are wondering why and how this month’s 1709 cumulative update is messing things up. Broken USB ports By far, the most common problem involves broken USB ports: Install this month’s cumulative update for Win10 Fall Creators Udpate, and your USB-connected devices stop working. There’s a lengthy discussion on AskWoody. One anonymous poster says: Been dealing with this on several machines today. I uninstalled the update, reboot (Which resolves the issue) then I re-apply the update, reboot and the USB devices work normally. It seems to effect random PCs. I see it more with USB devices that require 3rd party drivers. Rhherren goes on to say: Same issue here for us. Our team is having reports of USB devices not working after the login screen. The devices work fine in BIOS. Still no fix yet here for us. And many more. On the MSI (gaming notebook) forum, trongod says: I thought I would pass this information along. Tonight I had to reboot my laptop. After rebooting I lost my usb mouse and any device plugged into the USB ports. I went into my device manager and saw 3 devices that said drivers could not be found: MSI EPF USB USB Receiver USB Receiver I knew the night before a Windows 10 update was installed so I looked up the last update which was KB4074588. According to this site LAPTOPNINJA, it says the following: Addresses issue where the certutil.exe -MergePfx feature couldn’t produce a merged EPF file for multiple V1 certificates. Addresses issue where booting with Unified Write Filter (UWF) turned on may lead to stop error 0xE1 in embedded devices, particularly when using a USB HUB. Since both of those particular updates had both EPF and USB involved, I uninstalled the update. After that everything was working again. Looks like Microsoft is breaking stuff again and I don’t see any updated chipset drivers on the MSI site since the original. I may have to see if I can find something more up to date, try those and then attempt the update again. On Reddit, there are a few posts about the USB issue. Over on the Microsoft Answers forum, Damian Twyman reports a different problem: My PC did an automatic update this morning which took nearly 2 hours. In completion, I am finding minimised windows are repainting top-down when maximising and I no longer can drag windows across the screens without momentary freezing.... The whole computer is really slow...like it's thinking about things....shouldn't do because it's a oct core I7. This has annoyed me no end and really don't want these updates anymore because have lost many hours of trying to fix updates There’s a steady stream of non-replies from Microsoft that have infuriated more than a few. Context menus don't display text The litany of problems with KB 4074588 continues: Context menus don’t display text, the cmd window opens as a tiny window without any displayed text, various changed settings, no text under desktop icons, and on and on. Michael Cifuentes said it best: Got a new laptop with i7 because I needed some speed, no I need to finish some work and just can't thanks to your update, the laptop is running very slow and becoming impossible to use, When are you going to provide a solution? Can you at least acknowledge problem? Inaccessible boot device There’s yet another report concerning our old friend, the blue screen “Inaccessible boot device,” per VladeB: after installing KB4058258 I'm getting blue screen with Inaccessible boot device error. I was able to narrow it down to this servicing stack: C:\windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.212_none_17098c7c31fd065f It was installed by KB4058258 KB 4058258 is the Jan. 31 cumulative update for 1709. There’s one proposed, lengthy, workaround on AskWoody, but it’s complex, with four different scenarios: Some methods may have to be performed remotely because your USB ports aren’t working. Method 4 is the method for when nothing else can be done. ‘Softie Christopher Leung has asked for help in narrowing down the problem. Would it be possible for you to use these instructions and provide us with the necessary log to analyze the bug? We will try to get to the bottom of the issue as soon as possible. Clicking the link, I was pleasantly surprised to discover that Microsoft has a feedback procedure specifically for USB devices. If you’re having a USB problem after installing KB 4058258 (or January’s KB 4058258), please follow Leung’s procedure and submit your feedback to Microsoft. To my point of view, this big bug speaks volumes about Win10 Fall Creators Update suitability for deployment anywhere — not just in the enterprise. Pundits like to parrot Microsoft’s line that 1709 has been rolled out faster than any other version of Windows 10. This incident makes me think that 1709 just isn’t there yet. Let’s see what happens with the next 1709 cumulative update. In the meantime, I continue to recommend that you stay with Win10 Creators Update, version 1703. Assuming that you’re using Win10, anyway. Many thanks to Christopher Leung. Join use for finger wagging and head shaking on the new, souped-up AskWoody Lounge. Source: Buggy Win10 1709 cumulative update KB 4074588 redlining, bluescreening, borking USB (Computerworld - Woody Leonhard)
  4. Today is the 15th day this month that we’ve seen Windows patches, yanked patches, patches of patches and re-re-re-patches. Welcome to the third cumulative update for Win10 Fall Creators Update this month. Thinkstock/Microsoft Microsoft told us three weeks ago that Win10 Fall Creators Update, version 1709, was ready for enterprise deployment. Since then, we’ve seen the early January patch yanked because it tanked AMD machines. Then, after the first patch was reinstated, we got two more cumulative updates. In the past three weeks. I guess that’s what Microsoft now means by “Current Branch for Business” and/or “Semi-Annual Channel.” The latest salvo in the story arrived today with KB 4058258, which brings Windows 10 Fall Creators Update, version 1709, to build 16299.214. It’s headed out the Windows Automatic Update chute right now. Along with the 1709 cumulative update, we’re getting another “WaaSMedic” Remediation Shell, KB 4074608 — a Servicing Stack update released yesterday that, per @abbodi86 on AskWoody: Fixes and resets update-related parts to their “supported” configuration. It restores registry settings, services statuses, schedule tasks, it clears out disk space, and launches UpdateAssistant.exe if installed. Mainly it’s meant to pave the way to receive the latest updates, whether quality updates, or feature update to latest Windows 10 version It’s an MSI package not a regular update, doesn’t require a reboot. It has more than 12 releases so far. He goes on to say: Servicing Stack updates are bundled with cumulative updates in version 1709. You may notice that the 1709 SSU has a distinguished version (i.e. 16299.122.1.0), not the generic version like other updates before (i.e. 10.0.1.2). Servicing Stack updates won’t be listed in Windows Update history, but you can find it in Installed Updates Here’s this month’s hall of patching shame: Jan. 3 — The initial round of Meltdown/Spectre patches Jan. 4 — A re-issue of several Meltdown/Spectre patches Jan. 8 — Microsoft decides to pull Meltdown/Spectre patches for some AMD machines and releases a Win8.1/Server 2012 R2 Monthly Rollup Jan. 9 —56 “Patch Tuesday” patches arrive, many of them flawed Jan. 11 — New Meltdown/Spectre patches get released to some AMD machines, with no details on which ones Jan. 12 — “Unbootable state” patches for Win7, 8.1 (KB 4073578, etc.) show up Jan. 17 — 14 patches, mostly previews, arrive — along with two new Win10 cumulative updates Jan. 19 — Win10 cumulative update metadata changes (to alter installation logic) appear, along with a Win10 1709 preview Jan. 22 — There’s a fix for Outlook 2016 that lets you forward files attached to plain text messages Jan. 23 – The Win8.1 Preview Monthly Rollups are modified, apparently to avoid installing them on Win8.1 PCs running both PIC and APIC controllers. Jan. 24 — Standalone Win8.1 patch to fix crashes on PCs running both PIC and APIC controllers and a standalone Win7/.NET 4.7.1 patch to fix crashes using Windows Presentation Foundation. Jan. 26 -- .Net Quality Rollup preview KB 4054992 Jan. 29 -- Win10 1703 update component update KB 4073543 Jan. 30 -- Win10 1709 Servicing Stack Update KB 4074608 Jan. 31 -- Yet another Win10 1709 cumulative update KB 4058258 There’s also a newly updated KB article, KB 4073757, that covers many details with Windows, Meltdown and Spectre. It has lengthy lists of links to Security Advisories — Microsoft, Intel, AMD, Nvidia and more — guidance for all sorts of different kinds of hardware, a list of computer manufacturers — Acer, Dell, Epson, Fujitsu, HP, Lenovo, LG, NEC, Panasonic, Samsung, Toshiba and Vaio — with links to their advisories, and a promise of patches yet to come for Server 2012 and Server 2008 SP2. Something to look forward to. Join us for a CBB break on the AskWoody Lounge. Source: Perfect end to a perfect month: Yet another Win10 1709 cumulative update, KB 4058258 (Computerworld - Woody Leonhard)
  5. I am sure some know already, however sleep function seems to have been modified in the newest Windows Ten (10) version, 1709. Before, I would put P.C. into sleep, then when I wanted it out of sleep, I depress the touch space bar (or another key) and my desktop would appear after sign in. However, it now goes through a modified boot sequence avoiding for example the screen for Macrium Reflect that offers to restore or boot into windows and then desktop appears quickly and all startup items are there ready. Anyone else found this has happened and is there a way to stop the new sleep mode?
×
×
  • Create New...