Jump to content

Search the Community

Showing results for tags 'windows'.



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 884 results

  1. ------------------------------------------------------------------------------------------------------------------ Activation Type Supported Product Activation Period ------------------------------------------------------------------------------------------------------------------ Digital License - Windows 10 - Permanent KMS38 - Windows 10 / Server - Until the year 2038 Online KMS - Windows / Server / Office - For 180 Days, renewal task needs to be created for lifetime activation. ------------------------------------------------------------------------------------------------------------------ Read Me: File Details: File: MAS_0.8.7z Size: 1.06 MB (11,19,073 bytes) SHA-1: 5055e4dcdaa0bca19347d5867d73f2f835fc7c6a Download links: Password: 2019 Site: https://0x0.st Sharecode: /s3E Mirror: Site: https://tinyurl.com Sharecode: /yysd84n4 *If links are not working then try to enter the URL manually without copy pasting. (Due to bugs, this site adds ASCII hidden characters in text copying) ------------------------------------------------------ Screenshots Changelog Credits
  2. With one final April patch delivered in May, the time looks ripe to install last month’s patches. One antivirus manufacturer has a significant disagreement with Microsoft about the April patches, but you can easily bypass the problem — if you know the trick. Thinkstock/Microsoft April was a tough month for Win 7, 8.1, Server 2008 R2, 2012 and 2012 R2 customers who ran specific antivirus products. Blue screens, freezes, slow-as-sludge drippings all bedeviled a large number of Sophos, Avira, Avast, AVG and even McAfee users. Looks like we’re over that hump, with the AV manufacturers scurrying to fix their wares. Current state of AV Microsoft claims that it has “mitigated” (interesting choice of terminology) the blue screens and freezes with certain Sophos, McAfee and Avast (including AVG) products. In fact, if you check with the individual manufacturers' websites, they all claim to have shipped and installed fixes of various types that will allow Monthly Rollups and Security-only patches to proceed without gumming up the works. The one holdout? Avira. It’s a particularly interesting exception because Avira has claimed from the start that the April Win10 version 1809 cumulative update also clogged up the works with its antivirus product. I’ve seen rumors — but no definitive confirmation — that other AV products have had the same problem. At any rate, Avira at this point says it’s fixed everything: We have looked into the issue… and have found a way to fix it. We have recently released an update that should fix this issue. Your Avira Product will be automatically updated, and you don’t have to do anything else in the product. In a private communication, an Avira spokesperson says that Microsoft is no longer blocking the problematic patches on machines running Avira. Microsoft has a contrary opinion: Microsoft has temporarily blocked devices from receiving this update if Avira antivirus software is installed. … We are presently investigating this issue with Avira and will provide an update when available. There’s no mention on the Microsoft sites about slowdowns with the Win10 1809 patch. At this point, your best bet is to get Avira updated — manually if need be — and move on. I'd be willing to bet that the patches will install on updated Avira machines. (If you discover something contrary, hit me on AskWoody.com!) This whole incident left a bad taste in my mouth. As I mentioned before, whoever made the decision to release the six (now nine) problematic Windows patches either: Didn’t know they’d wreak havoc on millions of computers, or Didn’t care You can choose which one’s worse. More than that, the incident(s) exposed a bizarre behavior with Avast/AVG products: In order to update the software, you’re supposed to turn on your machine and do nothing for 15 minutes, while the AV package updates itself. As an anonymous poster on AskWoody put it: I have AVG and I have many items blocked in the firewall. Avast / AVG needs to have a way to manually download the patch from the AVG support download site and they need a warning to the person that an AVG update is about to commence, unblock or allow the files and registry keys to be modified. Updating in the background when the operator is away is not a good idea. Avast / AVG should be more transparent. The one Win7 patch to avoid Once again this month, you should studiously avoid KB 4493132, a Win7 patch that does nothing but nag you to move to Windows 10. Looks like the nag hasn’t had much effect, but why install it in the first place? It may be time for 1809 Although there are acknowledged problems with Win10 version 1809, they’re relatively minor. Given that Win10 version 1903 is nipping on our heels, I’m upgrading my Win10 machines to 1809. Better the devil ye ken. If you want to stay with 1803, it’s hard to blame you — the list of new features in 1809 reads like the ingredients list for a bottle of water. Mostly, if you move to 1809, you’re buying yourself six more months before you have to upgrade. Again. Woody Leonhard/IDG The safest way to move to 1809 is to run the “feature update” deferral down to zero and wait for Microsoft to take over. (See general instructions here.) That way the monkey’s on Microsoft’s back to make sure your machine is ready for 1809. Put the branch readiness level at “Semi-Annual Channel,” turn the feature update deferral to 0, and wait. If Microsoft figures your machine can take it, you’ll get 1809 sooner or later. But you won’t get 1903. Why? Even though Microsoft has changed the terminology, we’re assured “Semi-Annual Channel” will keep new versions off your machine until at least 60 days after release — and we’re told that 1903 won’t be released until the end of May. We've also been promised that Win10 1803 will sprout a new "Download and install" link — likely for both Home and Pro — by late May. We still haven't seen it in action, but if it works as promised, that'll be an enormous improvement over the blind-men-and-elephant approach we have right now. Update Here’s how to get your system updated the (relatively) safe way. Step 1. Make a full system image backup before you install the latest patches. There’s a non-zero chance that the patches — even the latest, greatest patches of patches of patches — will hose your machine. Best to have a backup that you can reinstall even if your machine refuses to boot. This, in addition to the usual need for System Restore points. There are plenty of full-image backup products, including at least two good free ones: Macrium Reflect Free and EaseUS Todo Backup. For Win 7 users, If you aren’t making backups regularly, take a look at this thread started by Cybertooth for details. You have good options, both free and not-so-free. Step 2. For Win7 and 8.1 If you have an antivirus product from Sophos, Avira, Avast, AVG or McAfee, make sure it’s up-to-date. Each product’s different. Yes, I know that many products from those vendors don’t have any problems — but it’s better to get buckled up anyway. Microsoft is blocking updates to Windows 7 and 8.1 on recent computers. If you are running Windows 7 or 8.1 on a PC that’s 18 months old or newer, follow the instructions in AKB 2000006 or @MrBrian’s summary of @radosuaf’s method to make sure you can use Windows Update to get updates applied. If you’re very concerned about Microsoft’s snooping on you and want to install just security patches, realize that the privacy path’s getting more difficult. The old “Group B” — security patches only — isn’t dead, but it’s no longer within the grasp of typical Windows customers. If you insist on manually installing security patches only, follow the instructions in @PKCano’s AKB 2000003 and be aware of @MrBrian’s recommendations for hiding any unwanted patches. For most Windows 7 and 8.1 users, I recommend following AKB 2000004: How to apply the Win7 and 8.1 Monthly Rollups. Realize that some or all of the expected patches for April may not show up or, if they do show up, may not be checked. DON'T CHECK any unchecked patches. Unless you're very sure of yourself, DON'T GO LOOKING for additional patches. In particular, if you install the April Monthly Rollups or Cumulative Updates, you won’t need (and probably won’t see) the concomitant patches for March. Don't mess with Mother Microsoft. If you see KB 4493132, the “Get Windows 10” nag patch, make sure it’s unchecked. Watch out for driver updates — you’re far better off getting them from a manufacturer’s website. After you’ve installed the latest Monthly Rollup, if you’re intent on minimizing Microsoft’s snooping, run through the steps in AKB 2000007: Turning off the worst Win7 and 8.1 snooping. If you want to thoroughly cut out the telemetry, see @abbodi86’s detailed instructions in AKB 2000012: How To Neutralize Telemetry and Sustain Windows 7 and 8.1 Monthly Rollup Model. Realize that we don’t know what information Microsoft collects on Window 7 and 8.1 machines. But I’d be willing to bet that fully-updated Win7 and 8.1 machines are leaking almost as much personal info as that pushed in Win10. Step 3. For Windows 10 You can follow the steps at the beginning of this article to leave your machine open for updating to Win10 version 1809 (my new current preference). When Win10 version 1903 appears we’ll have full instructions for blocking it. Of course, all bets are off if Microsoft, uh, forgets to honor its own settings. If you want to stick with your current version of Win10 — a reasonable alternative — you can follow my advice from February and set “quality update” (cumulative update) deferrals to 15 days, per the screenshot. If you have quality updates set to 15 days, your machine already updated itself on April 24. Don’t touch a thing and in particular don’t click Check for updates. Woody Leonhard/IDG For the rest of you, including those of you stuck with Win10 Home, go through the steps in "8 steps to install Windows 10 patches like a pro." Make sure that you run Step 3, to hide any updates you don’t want (such the Win10 1809 upgrade or any driver updates for non-Microsoft hardware) before proceeding. These steps will change drastically when Win10 1903 starts rolling out, particularly if Microsoft keeps its promise about "Download and install now." Stay tuned for details. Thanks to the dozens of volunteers on AskWoody who contribute mightily, especially @sb, @PKCano, @abbodi86 and many others. We’ve moved to MS-DEFCON 4 on the AskWoody Lounge. Source: Now’s the time to install the April Windows and Office patches (Computerworld - Woody Leonhard)
  3. Microsoft published a new support page on its Docs website that provides administrators and users with information about known issues and fixed issues for Windows. The page, which is titled Windows 10 release information, includes information for Windows 10, Windows Server, and previous versions of Windows including Windows 8.1 and Windows 7. If you check the issues of the current version of Windows 10, Windows 10 version 1809, you will find a list of current and resolved known issues listed on the page. Each issue is listed with a summary, the update it originated in, the status, and last update. Links point to the KB article of the update and to additional details on the Windows 10 Release Information page. Note: The formatting of the table is fixed, it appears which means that you may not see all columns of the table on the page. A click on the details link jumps to a section on the same page that describes the issue in detail. There you find information about affected platforms, workarounds, and other information that may help you mitigate the issue ore solve it. Microsoft lists Windows 10 version 1507 to 1809, Windows Server 2019 and 2016, Windows 7 SP1, Windows 8.1, and Windows Server 2008 R2, 2012 R2 and 2012 on the page currently. Windows 7, 8.1 and the old server versions are listed under previous versions on the page. The May 2019 Update release will see Windows 10 version 1903 added to the page. That's not all though; you find a message center listed on the page that lists recent announcements. These announcements provide important information from Microsoft teams and employees in regards to Windows. Recent announcements include an article on the benefits of Windows 10 Dynamic Updates, information that Windows Server 2008 R2 systems need a servicing stack update to add support for SHA-2 code signing, or that Windows 10 version 1809 is designated for broad deployment. These announcements are posted on various blogs and sites that Microsoft maintains. Closing Words The Windows 10 Release Information page is a useful addition as it collects information from various sources and displays them all in a single location. Instead of having to browse dozens of pages to find relevant information, administrators and users find them in a single location. Known issues alone is useful, as you find all known issues for all supported versions of Windows there. Summaries, descriptions, and links provide all the information that is available in a single location. The message center offers useful information from Microsoft. While you can follow teams and blogs using various methods -- not all support RSS or email notifications -- it is quite the hassle to stay up to date when it comes to vital Windows related information. The message center does not support RSS, unfortunately, but you can use a website monitor like Distill for web browsers, Web Alert for Android, or these site monitoring tools. The usefulness of the resource depends on the update frequency. If Microsoft manages to update the page regularly and shortly after information become available, it could very well become one of the best resources for Windows administrators and users (apart from this blog, of course). Source: Bookmark Tip: Windows Release Information by Microsoft (gHacks - Martin Brinkmann)
  4. First a quote from Microsoft Developer Network's (MSDN) support article: As you most probably already use Hyper-V and have a version or two of Windows installed on its virtual machines (judging by the fact that you found here), we can use a shortcut simplifying the process and use already existing VHD files of your Windows virtual machines. There's nothing wrong in running your Windows virtual machines as intended in Hyper-V. However, sometimes you might want unrestricted access to physical hardware on your host machine. Native boot gives you exactly that: when a VHD with Windows installed on it is used for native boot in a dual / multiple boot scenario, it will no longer use Hyper-V emulated, virtualized hardware devices but is instead as any operating system installed directly to physical hardware. In this tutorial we will add a Windows 10 Pro virtual machine's virtual hard disk file to my Windows 10 boot menu, to be able to choose which of the two Windows systems will be started when the machine will be booted. The tutorial might look a bit complicated but I assure you, this is really easy and fast. You set up your virtual machine's VHD for native boot in a minute :). Notice that you can use the method told in this tutorial on both BIOS (MBR) and UEFI (GPT) systems, mounting both MBR partitioned Generation 1 VHD files and GPT partitioned Generation 2 VHD files regardless if the host is MBR or GPT partitioned. A VHD from Generation 2 UEFI vm can boot natively on a BIOS (MBR) host, and a VHD from Generation 1 BIOS vm boots without an issue on UEFI (GPT) host. This method can be used to natively boot VHD files from Hyper-V virtual machines running Windows 8.1, Windows 10, Windows Server 2012 R2 or Windows Server 2016. Part One Preparations A Hyper-V virtual machine when created and before any checkpoints have been made consists of one VHD or VHDX file, a Virtual Hard Disk file. Later on when you for security or other purposes make checkpoints, Hyper-V adds a so called child VHD to the vm. As geeks love difficult words, we say this vm is from now on using differencing disk. It means that we have a base disk (also called parent disk), in Hyper-V usually a .vhdx file, and for that base a child disk with extension .avhdx, letter A coming from word automatic meaning it is managed automatically by Hyper-V without user interaction. In other words, keep your hands away, don't move, rename or delete them manually, only use Hyper-V Manager for any changes. Here's a screenshot of a typical Hyper-V vm (#1) and its checkpoints (#2), I have also pasted an extract from my virtual hard disk folder into this screenshot (#3): I created the vm and installed Windows in a .vhdx file (yellow highlight). When I made first checkpoint, the differencing data was stored in first .avhdx file (blue highlight), next checkpoint created again a differencing .avhdx to store changes since first checkpoint and so on. To get our vm to boot natively outside Hyper-V, we need to merge existing checkpoints (child disks) to base disk (parent). Native boot with a VHD or VHDX file is only possible if it has no child disks. Unfortunately this also means that when you remove the VHD or VHDX from native boot menu and continue using it in Hyper-V, you no longer have any checkpoints and can't restore the vm to earlier state. Think how important your checkpoints are, you wont get them back once deleted and merged to parent! 1.1) If the vm you want to use in native boot has any checkpoints, select the first checkpoint, right click and select Delete Checkpoint Subtree to remove all checkpoints. Hyper-V merges the data they contain to base disk and finally removes the child disks: 1.2) You can leave the .vhd or .vhdx file in its current location, or copy it to another drive. You can even copy the virtual hard disk to another computer and use it on that computer for native boot. If your intention is to continue using it also in Hyper-V in addition to native boot, leave it where it is 1.3) Download and install the free Macrium Reflect. Although mostly known of its disk imaging and cloning capabilities, Macrium also offers the easiest way to fix Windows boot records. We will use it later in Part Four to reset Windows boot records and boot menu Macrium Reflect Free download: Macrium Reflect Free Part Two Add VHD to boot menu 2.1) Open your virtual hard disks folder, default location if you have not changed it in Hyper-V settings is C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks 2.2) Double click the VHD file you want to boot natively and add to boot menu. This mounts the VHD on your host system. In this example I have copied the virtual hard disk to another computer and double click it to mount it to the host system: 2.4) Windows now mounts all partitions of this disk to host. Because the Hyper-V vm on this disk was setup as Generation 1 (BIOS / MBR partitioning), my host now shows two new drives, drive G: which is the system reserved partition of Windows 10 installation on that virtual hard disk, and drive H: which is the Windows partition of that installation: Notice that the VHD will be automatically unmounted when we restart in step 2.9; it only needs to be mounted now to be added to boot menu, later on there's no need to mount it. 2.5) Old school geek as I am, I always need to check. I open drive H: to see it really contains the virtual Windows 10 installation I want to use in native boot: 2.6) Open an elevated (admin) Command Prompt, type bcdboot H:\Windows and press Enter (replace drive letter H with actual drive letter for the mounted virtual hard disk containing Windows): 2.7) To prepare for the unexpected, to easily restore the default boot records let's not continue before we have added Macrium Rescue WinPE system to the boot menu. Start Macrium Reflect, open Other tasks menu, select Add Recovery Boot Menu Option: 2.8) Select Windows PE 10.0 menu and click OK, accept all possible prompts: 2.9) Restart Windows. You will be shown the Windows 10 boot menu Optional: 2.10) The physical PC, a laptop in this case has now been booted with a virtual hard disk from a Hyper-V virtual machine. It now uses the physical hardware and can access all host machine resources. Our virtual Windows is now physical (blue highlighted disk), with access to original host Windows hard disks (yellow): 2.11) If we check Disk Management we will see that the VHD was added as last hard disk, in this case Disk 3. Checking its properties we can clearly see that we are dealing with a virtual disk: OK, let's boot back to host, the original Windows installation by restarting and selecting it from boot menu 2.12) For your own comfort it might be a good idea to rename boot menu operating systems, the boot menu showing two identical "Windows 10" entries can be confusing. To do that open an elevated (admin) Command Prompt, type bcdedit and hit Enter. Boot records will be shown. Scrolling down the list you will find an entry titled Windows Boot Loader for each of our three operating systems. We are interested in three details on each entry: Identifier (yellow highlight in below screenshot), Device (blue) and Description (green): 2.13) As we have two identical "Windows 10" entries, lets change the VHD entry's name to something more descriptive. Checking the Device type in all three entries we can see that our VHD's Identifier is {default}. The command syntax to change the boot menu description is bcdedit /set {Identifier} description "AnyName". In this example I changed its name to My VHD with command bcdedit /set {default} description "My VHD": Looking better, easier to understand which entry starts what OS: Part Three Remove VHD from boot menu 3.1) I played with another VHD, this time Windows 8.1 but would like to remove it now from boot menu: 3.2) Open elevated (admin) Command Prompt, type bcdedit and hit Enter, browse to Windows Boot Loader entry you want to remove, note the identifier (Windows 8.1 VHD identifier highlighted): 3.3) Type bcdedit /delete {Identifier}, hit Enter to remove the VHD from boot menu: Note There are three different identifiers: The chosen default OS has identifier {default}, the current OS you are signed in at the moment is {current}. All other entries have a long hexadecimal identifier, as in this example the Windows 8.1 VHD identifier above. Typing these long hexadecimal strings is both boring and also might easily be typed wrong. In Command Prompt you can just select the string with mouse and hit Enter to copy it to Clipboard, then paste it to your command. Part Four Troubeshooting, reset boot menu 4.1) Anything can happen. A restart can suddenly show this when you select an OS from boot menu (in screenshots current Windows 10 recovery prompt and old style legacy prompt which can be shown depending on if you have manually changed to legacy boot menu, or added Windows 7 or older OS on multi boot system): This does not happen often but when it happens you might be unable to boot to any of the installed operating systems except Macrium WinPE rescue system which we added to boot menu in steps 2.7 and 2.8. In modern prompt, press F9 to open boot menu. In old style prompt press Enter. You can now select another operating system from menu, or use Macrium to fix boot records as told below (if you did not add Macrium to Windows Boot Menu, restart your PC now booting from Macrium boot disk / USB and continue from 4.3). 4.2) Select Macrium Reflect System Recovery and hit Enter: 4.3) When Macrium has started, select Fix Windows boot problems top left: (Screenshot from a BIOS system, process exactly the same in UEFI.) 4.4) Click Next: 4.5) Click Next: 4.6) Click Finish: 4.7) Click Yes: 4.8) Windows boot records have been reset, your original physical Windows 10 installation will start, no boot menu is shown. To continue playing with native boot you have to add your VHD files again as well as the Macrium rescue boot option as told in Part Two. Note When boot records have been reset with Macrium as told in Part Four above, your Hyper-V virtual machines might not start telling you that one of the Hyper-V components is not running: By reseting boot records Macrium has caused the hypervisor not to work properly. Luckily this is not an issue, we can fix it easily. Simply give this command in an elevated Command Prompt and restart your Hyper-V host PC: Code: bcdedit /set hypervisorlaunchtype auto Hyper-V virtual machines will again run without issues. Information You can naturally also reset your boot records whenever you want to, when you no longer want to boot to your VHD files. Notice that you can update Windows on the natively booted VHD normally, install software, do everything else but you cannot upgrade it to next builds: When / if you want to upgrade, boot to your original host OS, run the VM in Hyper-V and upgrade. When done you can again boot to it using the method told in this tutorial. Tenforums.com
  5. We waited an extra 10 days for this? Microsoft has released its second monthly patches for Windows. Oddities abound, but there’s no fix for the mammoth bluescreen antivirus conflict in Win7 or 8.1, and precious little improvement unless you’re using Japanese calendars. Franck V. (CC0) Microsoft usually releases patches on Tuesdays at 10 a.m. Redmond time. So it came as something of a surprise when we saw the second round of April patches rolling out on the fourth Thursday of the month at 2:30 p.m. Admins, who have come to expect this kind of erratic behavior, are pulling out more gray hair. I could understand if the Fourth Tuesday patches included something critical that required last-minute tweaking. But…, Microsoft. Here’s a rundown of this month’s second-wave patches: Win10 version 1809 - nothing. Delays in the 1809 patches are old news, but the usual excuse involves extra testing in the Windows Insider Release Preview (beta testing) ring. This month, 1809 isn’t in the Release Preview ring. It’s just AWOL. Win10 version 1803 - cumulative update KB 4493437 has a bunch of little “quality” (non-security) fixes, plus 10 separate Japanese date bug fixes. The IE “Custom URI Schemes” bug introduced earlier has apparently been fixed. Both of the other acknowledged bugs are still there, including Rename on a Cluster Shared Volume crashing the system. Win10 versions 1709, 1703, 1607, 1507 - get equally ginormous volumes of little fixes, plus 10 or 11 Japanese date bug fixes, depending on version. Windows 8.1, Server 2012 R2 - Preview of Monthly Rollup KB 4493443 contains seven Japanese date bug fixes and nothing else. Windows 7, Server 2008 R2 - Monthly Rollup Preview KB 4493453 has eight Japanese date bug fixes and bupkis. There are also similarly stunted Monthly Rollup Previews for Server 2008 SP2 and Server 2012, as well as non-cumulative Security-only patches for Win 8.1 and Win 7. The latter contain 17 separately identified Japanese calendar-related fixes -- and nothing else. All of these patches are reserved for those who either specifically select them in Windows Update, download and install them manually, or (shudder) click "Check for updates." Microsoft’s been trying to fix the Japanese calendar every couple of weeks for almost a year. Guess it’s a hard Computer Science problem. Most disconcerting, at least to me, is that there appears to be no resolution to the “dirty six” Win 7 and 8.1 patches released earlier this month that bluescreened PCs running various antivirus programs. Microsoft has promised that Win10 1809 and 1803 would grow a new way to block the installation of Win10 1903, via an opt-in link called Download and install now. I don’t see any hint of that feature just yet. You have to ask yourself why all of these lame patches took so long – and when (or if!) we’ll see a Win10 1809 patch. Join the night watch on the AskWoody Lounge. Winter is coming. Source: Second-wave April Windows patches arrive, not with a bang, but a Japanese whimper (Computerworld - Woody Leonhard)
  6. Hash Check Via MSDN: http://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#searchTerm=Windows%208.1%20with%20Update&ProductFamilyId=0&Languages=en&PageSize=10&PageIndex=0&FileId=0 Details: November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2: New features and improvements/List of the fixed issues: Windows 8.1 RTM Installations-Keys Full versions : Core/Standard .......: 334NH-RXG76-64THK-C7CKG-D3VPTProfessional ........: XHQ8N-C3MCJ-RQXB6-WCHYG-C9WKBProfessional WMC ....: GBFNG-2X3TC-8R27F-RMKYB-JK7QTProfessional VL .....: GCRJD-8NW9H-F2CDX-CCM8D-9D6T9Professional VL WMC .: 789NJ-TQK6T-6XTH8-J39CJ-J8D3PEnterprise ..........: FHQNR-XYXYC-8PMHT-TV4PH-DRQ3HN-versions:Core/Standard N .....: 6NPQ8-PK64X-W4WMM-MF84V-RGB89Professional N ......: JRBBN-4Q997-H4RM2-H3B7W-Q68KCProfessional VL N ...: HMCNV-VVBFX-7HMBH-CTY9B-B4FXYEnterprise N ........: NDRDJ-3YBP2-8WTKD-CK7VB-HT8KWAll Other Edition Installation Keys:http://pastebin.com/M5VV6750 Windows 8.1 with Update [November 2014 Rollup] - MSDN DVD ISO English FTP Direct Download Links #351 >>> Windows 8.1 with Update (multiple editions) - DVD (English) File: en_windows_8.1_with_update_x64_dvd_6051480.isoCRC-32: cd5bc9f1MD4: 86112ed6364204bc96a3046fd931b2cbMD5: e0d4594e56c0545d379340e0db9519a5SHA-1: a8b5df0b0816280ae18017bc4b119c77b6c6eb7magnet:?xt=urn:btih:df6c4765ded49d65a29bef89014bdb9ba3758f66&dn=en_windows_8.1_with_update_x64_dvd_6051480.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:DF6C4765DED49D65A29BEF89014BDB9BA3758F66&dn=en_windows_8.1_with_update_x64_dvd_6051480.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=http%3a%2f%2fbeta.mytracker.me%3a6969%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2fopen.demonii.com%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.prq.to%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce Windows 8.1 with Update (multiple editions) (x86) - DVD File: en_windows_8.1_with_update_x86_dvd_6051550.isoCRC-32: 86e3499fMD4: 0ff14bffabc4bf7c680c1df7c2936df2MD5: 46ce6553a0e0abc264b77c1fc59dfb29SHA-1: c7fa828e01e98b601e0aca8019f1cb223eb23223magnet:?xt=urn:btih:024e78a6f38386c5338fbdd7220cf92c32c452c1&dn=en_windows_8.1_with_update_x86_dvd_6051550.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:024E78A6F38386C5338FBDD7220CF92C32C452C1&dn=en_windows_8.1_with_update_x86_dvd_6051550.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=http%3a%2f%2fbeta.mytracker.me%3a6969%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2fopen.demonii.com%3a1337%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.prq.to%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce Windows 8.1 Pro Volume License with Update DVD (English) File: en_windows_8.1_pro_vl_with_update_x64_dvd_6050880.isoCRC-32: a466193aMD4: 3f14a3a7125cf282a97b9ca4f04c62a7MD5: 2b57629165900f93e73305ddf27124d4SHA-1: 962a1d890987b5877469433928b8c8b8a3e945cdmagnet:?xt=urn:btih:12e023cc81dd4981363aaf78de9b36eecb0c51c3&dn=en_windows_8.1_pro_vl_with_update_x64_dvd_6050880.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:12E023CC81DD4981363AAF78DE9B36EECB0C51C3&dn=en_windows_8.1_pro_vl_with_update_x64_dvd_6050880.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce Windows 8.1 Pro VL with Update (x86) - DVD (English) File: en_windows_8.1_pro_vl_with_update_x86_dvd_6050918.isoCRC-32: 4ce30039MD4: 04cb297e1704de7e7bf91280c8d652a8MD5: a4355ab46a40fd343deb0a534e4a4823SHA-1: e46f44cd74f812ec3fe2e854317a088e85322a68magnet:?xt=urn:btih:2c9f99876a177185ac17be522e9861f6485d159f&dn=en_windows_8.1_pro_vl_with_update_x86_dvd_6050918.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:2C9F99876A177185AC17BE522E9861F6485D159F&dn=en_windows_8.1_pro_vl_with_update_x86_dvd_6050918.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce Windows 8.1 Enterprise with Update - DVD (English) File: en_windows_8.1_enterprise_with_update_x64_dvd_6054382.isoCRC-32: 524fc31eMD4: e5005b0d5943956c6bf60a2e436c5d58MD5: 115d7c4203417e52c09d16b50043b10dSHA-1: b7dd748446d89b9449a160cdc24bd282989bbd96magnet:?xt=urn:btih:a5051cf4aaf1e3f5a66ce44bbdd050f7142ed30d&dn=en%5Fwindows%5F8.1%5Fenterprise%5Fwith%5Fupdate%5Fx64%5Fdvd%5F6054382.iso&tr=udp://open.demonii.com:1337/announcemagnet:?xt=urn:btih:a5051cf4aaf1e3f5a66ce44bbdd050f7142ed30d&dn=en_windows_8.1_enterprise_with_update_x64_dvd_6054382.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:A5051CF4AAF1E3F5A66CE44BBDD050F7142ED30D&dn=en_windows_8.1_enterprise_with_update_x64_dvd_6054382.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce Windows 8.1 Enterprise with Update (x86) - DVD (English) File: en_windows_8.1_enterprise_with_update_x86_dvd_6050710.isoCRC-32: 31592527MD4: 68d0bb22e86bd92263ebfda5ef9fad21MD5: ce18de710a9c025323b8dee823bfbe7bSHA-1: 584a9ad7e2bb3d7e189adcfba44a497cc9155937magnet:?xt=urn:btih:c6b8fd001232c5a4662ccad3b09d933710af6632&dn=en%5Fwindows%5F8.1%5Fenterprise%5Fwith%5Fupdate%5Fx86%5Fdvd%5F6050710.iso&tr=udp://open.demonii.com:1337/announcemagnet:?xt=urn:btih:c6b8fd001232c5a4662ccad3b09d933710af6632&dn=en_windows_8.1_enterprise_with_update_x86_dvd_6050710.isoOr with Public Tracker Magnet Linkmagnet:?xt=urn:btih:C6B8FD001232C5A4662CCAD3B09D933710AF6632&dn=en_windows_8.1_enterprise_with_update_x86_dvd_6050710.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounceOr Multi Collection Magnet Link:magnet:?xt=urn:btih:2F7D04E7F4B3D29AEF3AB54D86016B47A80AE7B8&dn=Windows%208.1%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdbb48cbaace76c0eed6f2ec311%2fannounce ---------------------------------- * N Edition(s) * ---------------------------------- Windows 8.1 N with Update (multiple editions) - DVD (English) File: en_windows_8.1_n_with_update_x64_dvd_6051677.isoCRC-32: 0c6a8abaMD4: a2dc46badcc9e7222a4ad685c4d7797eMD5: 233e312a97f03b35010b6dbbac9e6044SHA-1: 457d02bd26a19965da172daae78f985cf53af692magnet:?xt=urn:btih:2f8a84ed6884457d5630f40ecc4248fba77f77b6&dn=en_windows_8.1_n_with_update_x64_dvd_6051677.isomagnet:?xt=urn:btih:2F8A84ED6884457D5630F40ECC4248FBA77F77B6&dn=en_windows_8.1_n_with_update_x64_dvd_6051677.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce Windows 8.1 N with Update (multiple editions) (x86) - DVD (English) File: en_windows_8.1_n_with_update_x86_dvd_6051704.isoCRC-32: c54e74adMD4: e08c72c71ff802909962ec27830e94ebMD5: 19396aa74f220546f49bd7d912ae9613SHA-1: a2c2d9916a4aee87afdd0aea19459f2f8414737cmagnet:?xt=urn:btih:f2b86d30cde3d01553e74dedca57d4a2af03558b&dn=en_windows_8.1_n_with_update_x86_dvd_6051704.isomagnet:?xt=urn:btih:F2B86D30CDE3D01553E74DEDCA57D4A2AF03558B&dn=en_windows_8.1_n_with_update_x86_dvd_6051704.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce Windows 8.1 N Pro VL with Update - DVD (English) File: en_windows_8.1_pro_n_vl_with_update_x64_dvd_6050969.isoCRC-32: 7fd3792dMD4: d7cf74125c320da14a941051d2afa372MD5: a047785bb6185dc77ee704f3504bda2cSHA-1: 169b23ac9f222426741f260607e090f327c03021magnet:?xt=urn:btih:b55e8fcac6e9a3ed828fcc906e4a844e85036461&dn=en_windows_8.1_pro_n_vl_with_update_x64_dvd_6050969.isomagnet:?xt=urn:btih:B55E8FCAC6E9A3ED828FCC906E4A844E85036461&dn=en_windows_8.1_pro_n_vl_with_update_x64_dvd_6050969.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce Windows 8.1 N Pro VL with Update (x86) - DVD (English) File: en_windows_8.1_pro_n_vl_with_update_x86_dvd_6051127.isoCRC-32: 1afbb41cMD4: 4b2816dc9058017de71085017833a770MD5: 36cfcecf1c7817976a2f42d06092b617SHA-1: ea571feb0ad31f1daa4916f161dc87416d8690camagnet:?xt=urn:btih:6dc4a106185e640a67d0105af951f63b21576eb9&dn=en_windows_8.1_pro_n_vl_with_update_x86_dvd_6051127.isomagnet:?xt=urn:btih:6DC4A106185E640A67D0105AF951F63B21576EB9&dn=en_windows_8.1_pro_n_vl_with_update_x86_dvd_6051127.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce Windows 8.1 Enterprise N with Update - DVD (English) File: en_windows_8.1_enterprise_n_with_update_x64_dvd_6050225.isoCRC-32: 7b73f762MD4: 7700c9878a61eeb98c8a0754d3c0a8f8MD5: 3dd3707820473dfa2adff73b2c44d4f3SHA-1: 33e141a1a7f02b4b3b4f590fb5ae47b71f18c3b8magnet:?xt=urn:btih:55208160763ccd10206f8952a96991835fc78e4f&dn=en%5Fwindows%5F8.1%5Fenterprise%5Fn%5Fwith%5Fupdate%5Fx64%5Fdvd%5F6050225.iso&tr=udp://open.demonii.com:1337/announcemagnet:?xt=urn:btih:55208160763ccd10206f8952a96991835fc78e4f&dn=en_windows_8.1_enterprise_n_with_update_x64_dvd_6050225.isomagnet:?xt=urn:btih:55208160763CCD10206F8952A96991835FC78E4F&dn=en_windows_8.1_enterprise_n_with_update_x64_dvd_6050225.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce Windows 8.1 Enterprise N with Update (x86) - DVD (English) File: en_windows_8.1_enterprise_n_with_update_x86_dvd_6050217.isoCRC-32: 3d8eee43MD4: b4007d7e4b7688ac036b5f090c418d92MD5: 826a4b6107f78e1e3310185534dc5155SHA-1: e4651c6ed8b6e5ad30da429a1dfb4be8760504f0magnet:?xt=urn:btih:a867941e07ad4f6e2e880b0850d8cd2181342921&dn=en%5Fwindows%5F8.1%5Fenterprise%5Fn%5Fwith%5Fupdate%5Fx86%5Fdvd%5F6050217.iso&tr=udp://open.demonii.com:1337/announcemagnet:?xt=urn:btih:a867941e07ad4f6e2e880b0850d8cd2181342921&dn=en_windows_8.1_enterprise_n_with_update_x86_dvd_6050217.isomagnet:?xt=urn:btih:A867941E07AD4F6E2E880B0850D8CD2181342921&dn=en_windows_8.1_enterprise_n_with_update_x86_dvd_6050217.iso&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannouncemagnet:?xt=urn:btih:07F0BF62E1510171E9E4A477EDCBF0A75DAE84B2&dn=Windows%208.1%20N%20with%20Update%203%20%28English%29&tr=http%3a%2f%2fbt.nnm-club.info%3a2710%2f002e7cdb7ba87f9f4d7dde0bb759b601%2fannounce ---------------------------------- * Windows 8.1 Language Pack with Update (Multiple Languages) * ---------------------------------- Languages: English, Japanese, Korean, Arabic, Bulgarian, Czech, Danish, German, Greek, Spanish, Estonian, Finnish, French, Hebrew, Croatian, Hungarian, Italian, Lithuanian, Latvian, Dutch, Norwegian, Polish, Portuguese-Brazil, Romanian, Russian, Slovak, Slovenian, Serbian, Swedish, Thai, Turkish, Ukrainian, Chinese - Hong Kong SAR, Chinese - Simplified, Portuguese-Portugal Windows 8.1 Language Pack with Update - DVD (Multiple Languages) File Name: mu_windows_8.1_language_pack_with_update_x64_dvd_6066963.isoSHA1: 70940468031652C3E7384AB92D4F7969FBF5A004magnet:?xt=urn:btih:BFCC5C9B8D97F4758622025E92F70FE970663726magnet:?xt=urn:btih:B21CC217C3A836FD12E57F3BCC7CFD72E8996A2Cmagnet:?xt=urn:btih:BFCC5C9B8D97F4758622025E92F70FE970663726&dn=mu_windows_8.1_language_pack_with_update_x64_dvd_6066963.iso&tr=http%3a%2f%2fannounce.torrentsmd.eu%3a6969%2fannounce.php%3fpasskey%3d1d5007ada34c95a6523ba4e4458cd7ec&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.me%3a8080%2fannounce.php%3fpasskey%3d1d5007ada34c95a6523ba4e4458cd7ec Windows 8.1 Language Pack with Update (x86) - DVD (Multiple Languages) File Name: mu_windows_8.1_language_pack_with_update_x86_dvd_6066964.isoSHA1: B6EAC4C1F57493C5B6F67A20A214BF4B0B62BF59magnet:?xt=urn:btih:5BECDDB1EA903A24BCA157EC843FFD35010E8C0Bmagnet:?xt=urn:btih:B21CC217C3A836FD12E57F3BCC7CFD72E8996A2Cmagnet:?xt=urn:btih:5BECDDB1EA903A24BCA157EC843FFD35010E8C0B&dn=mu_windows_8.1_language_pack_with_update_x86_dvd_6066964.iso&tr=http%3a%2f%2fannounce.torrentsmd.eu%3a6969%2fannounce.php%3fpasskey%3d1d5007ada34c95a6523ba4e4458cd7ec&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.me%3a8080%2fannounce.php%3fpasskey%3d1d5007ada34c95a6523ba4e4458cd7ec ------- * Windows Server 2012 R2 with Update [November 2014 Rollup] - MSDN Edition(s) * -------- [English l Release Date: 12/15/2014] Hash Check Via MSDN: http://msdn.microsoft.com/en-us/subscriptions/downloads/default.aspx#searchTerm=Windows%20Server%202012%20R2&ProductFamilyId=0&Languages=en&PageSize=10&PageIndex=0&FileId=0 Windows Server 2012 R2 Installations-Keys: Windows Server 2012 R2 with Update (x64) - DVD (English) Windows Server 2012 R2 VL with Update (x64) - DVD (English) Windows Storage Server 2012 R2 & Windows Server 2012 R2 Foundation with Update x64 DVD (English) Windows Server 2012 R2 Essentials with Update (x64) - DVD (English) --------------------------------- * Windows Server 2012 R2 Language Pack with Update (Multiple Languages) * ---------------------------------- Languages: Windows Server 2012 R2 Language Pack with Update (x64) - DVD (Multiple Languages) ---------------------------- * Windows Embedded 8.1 Industry with Update Edition(s)* ---------------------------------- Windows Embedded 8.1 Industry Installations-Keys: Embedded=6Q7P9-NFD2F-7JGQR-3X277-9BQMREmbeddedEval=VV6W8-NF7BJ-FKHGQ-P424D-FHC7KEmbeddedAutomotive=J2ND2-BCW98-8669Y-HPBF3-RDY99EmbeddedE=MNKW8-HYCCD-G88JY-283WV-W9FX9EmbeddedEEval=VKKC6-NQQQH-JW3QX-XRVKX-KJJK9EmbeddedIndustry=GN7VX-YKPC2-XY98J-9RYKX-KP9HVEmbeddedIndustryA=TP7MN-9H7FK-P4PJM-K6KJT-Y97RYEmbeddedIndustryE=NDXXJ-YX29Q-JDY6B-C93G8-TQ6WHEmbeddedIndustryEEval=PPBKC-NQYJM-JJ8X6-26W42-VFQ4REmbeddedIndustryEval=XDJ76-KNBM8-BB9BK-B4CHH-XD6VRAll Edition Installation Keys: http://pastebin.com/M5VV6750 Windows Embedded 8.1 Industry Enterprise & Pro with Update (x64/x32) - DVD (English) magnet:?xt=urn:btih:e4697090636dd157ab6e1eab46fc3ce7bdb06de6 magnet:?xt=urn:btih:E4697090636DD157AB6E1EAB46FC3CE7BDB06DE6&dn=en_Windows_8.1_Embedded_with_Update_3&tr=http%3a%2f%2f94.228.192.98%2fannounce&tr=http%3a%2f%2fannounce.torrentsmd.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.jamendo.com%3a80%2fannounce&tr=http%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=http%3a%2f%2fretracker.local%2fannounce&tr=http%3a%2f%2ftracker.blazing.de%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce&tr=udp%3a%2f%2f10.rarbg.com%2fannounce&tr=udp%3a%2f%2fbt.rghost.net%3a80%2fannounce&tr=udp%3a%2f%2ftracker.token.ro%3a80%2fannounce&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounce Credit & Thanks to: Threat, GezoeSloog, Paul [MDL]ru-board, NNM-Club also every nsane members contributing download links & discussion. : ) Some Of the Important Direct l Magnet l Torrent Download Links: * Be caution some links may be removed or Remote Upload may fail to order to get the original MSDN Hash etc... *
  7. April 2019 Windows patches wreaked havoc on many PCs, with crashes linked to Sophos, Avast and Avira products and debilitating slowdown reports on Win10 1809 machines. Who’s testing this stuff? Ends up the answer isn’t all that simple. Thinkstock/Microsoft This month’s Patch Tuesday sent many Windows users running for cover. As I reported on Wednesday morning, Win7 and 8.1 machines running Sophos antivirus products frequently refused to boot. The dragnet has since expanded, with both Avira and Avast now admitting their products are having problems, and rumors are swirling about many other antivirus manufacturers. You have to ask: Who’s testing this stuff? In a nutshell, we’ve seen PC-breaking behavior with all of these April patches: Win7 and Server 2008 R2 Monthly Rollup (KB 4493472) and Security-only (KB 4493448) patches Win8.1 and Server 2012 R2 Monthly Rollup (KB 4493446) and Security-only (KB 4493467) patches Server 2012 Monthly Rollup (KB 4493451) and Security-only (KB 4493450 ) patches Microsoft has modified the Knowledge Base articles for all six of those patches to include the admonition: Microsoft and Sophos have identified an issue on devices with Sophos Endpoint Protection installed and managed by either Sophos Central or Sophos Enterprise Console (SEC) that may cause the system to freeze or hang upon restart after installing this update. Which is a bit disingenuous. In fact, Sophos, Avast and Avira have all reported problems with various combinations of those patches. I’ve seen an anonymous report that the Win7 patch interferes with McAfee virus definition updates. Nobody knows what to think because there's been no clear advice from Redmond. Microsoft now says that it ... has temporarily blocked devices from receiving this update if the Sophos Endpoint is installed until a solution is available. Spiceworks has a long-running thread on the screw-up. Much to their credit, both Sophos and Avast have named employees working on the reports. I’ve heard persistent rumors that Microsoft is also blocking the six patches on machines with other antivirus products (Avast? Avira? McAfee?) but there’s no official confirmation. If Microsoft had a solid reputation for reporting the antics of its installers, I’d be skeptical of the rumors. But, of course, Microsoft’s reputation is precisely the opposite. We’re coming up on three days after the bomb dropped, and we really have no idea. There’s an additional problem that’s starting to rear its ugly head. I’m seeing many reports of this month’s first cumulative update for Win10 version 1809, KB 4493509, slowing machines down to the point they’re unusable. Avira has mentioned this problem, too. Right now, with the background decibel level so high, it’s hard to know exactly what’s causing problems. But anyone running Windows 7, 8.1, Server 2008 R2, 2012, or 2012 R2 should be cautious. And Win10 version 1809 cumulative updates are always a crapshoot — as many of you can painfully attest. Why isn’t anybody testing this stuff? Good question, but there’s no easy answer. Clearly, there was some change in those six patches that broke a long-standing entry into the internals of Windows. Clearly, at least some Sophos, Avast and Avira products used the now-broken hook. Does Microsoft have the right to cut off a hole in Windows, even if it’s being used by antivirus vendors? Certainly. Do the antivirus vendors have a right to know about — be explicitly warned about — changes that are coming that’ll break their products? I would answer yes. Should everybody — Microsoft and the antivirus vendors — be testing this stuff before it’s released? Absolutely. We’re talking about major AV products here, with millions of users. We can point the finger in a dozen different directions, but there’s one sad fact: Whoever decided to release these six patches either a) didn’t know or b) didn’t care that they’d brick millions of machines. Which is worse? Doesn't matter. We, the customers, got screwed. All in all, it would be a very good idea to sit out this month’s patches until Microsoft and the AV vendors get their acts together. I know there are people who say you have to prioritize one patch or another — get those patches installed right away, bucko! — but at this point, unless you’re protecting state secrets, there’s no point in sticking your finger in the pencil sharpener. We’ve moved to MS-DEFCON 1 on the AskWoody Lounge. Source: This month’s Windows patching debacle gradually comes into focus (Computerworld - Woody Leonhard)
  8. Hello So i have a few apps that i've set them to start at windows start-up but they wont start right away but only after i've inserted my windows login details Is there a way, while i login to windows 10 for those apps to allready be started and ready ? Thanks
  9. With cumulative updates, monthly rollup updates, preview quality updates and more, Microsoft’s Windows update terminology is nearly indecipherable. We’re here to help. Microsoft / IDG All it took was one question. One question of 26 asked by Microsoft in a survey about experiences with Windows Update. That one question encapsulated the struggle Windows users deal with in updating and upgrading the operating system. What types of updates do you install? (Check all that apply.) That was the question. Microsoft offered five possible responses. IDG Microsoft's questionnaire asked participants to choose the types of updates they installed. But it didn't bother to define those choices. Five. Possible. Responses. Since Windows 10's introduction nearly four years ago, Microsoft has multiplied not only the number of updates — raising feature-changing upgrades by a factor of six, for instance — but has also increased the kinds of updates. Where once there was but a single kind of update, the kind that showed up each second Tuesday to patch vulnerabilities, now there are multiples, enough that Microsoft has come to label some with letters of the alphabet. Yet understanding the updates, knowing what is which and what for, is more important than ever, even if Microsoft doesn't pause to explain the differences. You need an update dictionary. We'll try our best to put some meat on the terminology bones, but honestly, Microsoft's lexicon is so obtuse, so confusing, so contradictory, so... well, we gave it a shot. We'll update — pun unintended — as necessary. Cumulative updates Microsoft defines "cumulative update" both as a collection of fixes — as when it describes it as something "in which many fixes to improve the quality and security of Windows are packaged into a single update" — and as an all-encompassing update that includes not only the latest changes but also all those from that product's past. "Each cumulative update includes the changes and fixes from all previous updates" is how Microsoft explains it. Not surprisingly, the two definitions overlap, but Microsoft's explainers have stressed one over the other when that's suited them. When Microsoft added Windows 7 to the we're-now-doing-cumulative-updates list, raising Cain among users who for decades could pick and choose which fixes to apply, the firm told them patching was now an all-or-nothing affair, emphasizing the "packaged into a single update" definition. The old way of patching "resulted in fragmentation, where different PCs could have a different set of updates installed, leading to multiple potential problems," said a Microsoft product marketing manager in 2016 as he announced the change. But the two broader definitions of "cumulative" were not what Microsoft was asking about in the survey. Instead, it was after feedback for "Cumulative," with a capital "C," in the questionnaire. In the Windows Update Catalog — an official distribution portal for all updates — "Cumulative" applies only to certain updates for Windows 10 and various server products, including Windows Server 2019 and Server 2016. They're typically distributed several times each month and always contain what Microsoft terms "quality improvements," which is fancy-talk for bug fixes. They sometimes include security patches for Windows vulnerabilities. Cumulative is a label Microsoft plasters on a lot of updates. The 64-bit version of Windows 10 1809, last year's troubled (and that's an understatement) feature upgrade, has been served six Cumulative updates so far this year, one each in February and April, and two each in January and March. IDG Windows 10 version 1809 has been served with half a dozen cumulative updates so far this year. Some include patches for security vulnerabilities, some don't. Security-only updates Also called "security-only quality update" (and no, we're not making this stuff up), these updates contain just one month's worth of security fixes for a single product — say, Windows 7. Microsoft's official definition reads, in part, "an update that collects all the new security updates for a given month and for a given product, addressing security-related vulnerabilities and distributed through Windows Server Update Services (WSUS), System Center Configuration Manager (SCCM) and Microsoft Update Catalog." What the description doesn't tell users is that, as far as we're able to tell, it's used only with the older OSes, Windows 7 and Windows 8.1, and their Windows Server companions, Server 2008 and Server 2012. Microsoft doesn't assign the term to any Windows 10 updates. Security-only updates are distributed on Patch Tuesday, the second Tuesday of each month, a day Microsoft prefers everyone dub "Update Tuesday," as if the word "patch" was objectionable. Because distribution is restricted to WSUS and SCCM (with the latter using the Update Catalog), and not via the consumer-grade Windows Update, security-only updates target businesses which want to plug security holes and that's it. Security-only updates are one of the few non-cumulative updates that Microsoft still distributes; skip one and multiple vulnerabilities will remain unpatched. This update class garnered the most attention when applied to Windows 7 three years ago, as it gave IT administrators a bit of the flexibility that had been stripped from them previously when Microsoft mandated cumulative updates. Note: "Security-only" does not necessarily mean "All security." Since early 2017, Microsoft has omitted security patches for Internet Explorer from the security-only updates issued to Windows 7 and Windows 8.1. Instead, they're distributed in their own, IE-only, cumulative update each month that a browser patch is required. Microsoft's rationale: Customers wanted smaller updates, and this was one way to accomplish that, the company said. However, Computerworld concluded that only those not running IE would realize size savings; the decision was an acknowledgement that Windows 7 and 8.1 customers had dumped IE. Monthly rollup updates Slapped with the officious label "Security Monthly Quality Update" in the Microsoft Update Catalog, these are the Oliver Hardy to the security-updates' Stan Laurel. Jack Sprat's wife to Jack himself. Not only do the monthly rollups include both security and non-security bug fixes, but unlike security-only updates, they're cumulative in that each includes the totality of past updates. So not surprisingly, they're significantly larger than the same month's security-only update. Microsoft defines them as "a tested, cumulative set of updates" — making one wonder what updates weren't tested — that are distributed via Windows Update, WSUS, SCCM and the Update Catalog. Like "security-only," the term "monthly rollup" (even Microsoft rarely deploys the mouthful "Security Monthly Quality Update" outside of Windows Update and the Update Catalog) is for older OSes only: Windows 7 and Server 2008, Windows 8.1 and Server 2012. We weren't able to find any instance of the name assigned to a Windows 10 update. (The term is used, though, to describe .NET updates suitable for Windows 10, so there's that.) Microsoft issues monthly rollups on Patch Tuesday. Even though Microsoft doesn't use the "monthly rollup" designation in Windows 10, that's essentially what "cumulative updates" are. Like monthly rollups, cumulatives include security and non-security bug fixes and contain all past adjustments, too. Side note: "Rollup" is a term Microsoft has used for decades to label catch-up updates, those that bring a program or operating system up to current status by bundling all past fixes. (Usually from a specific point in time — say, the last major release. These were once called "service packs" and abbreviated to "SP," as in "SP1" to designate the first such collection.) It's unclear why Microsoft repurposed the moniker for something that was not a catch-up, but a constant series instead. Preview quality updates Also known as "Preview of Monthly Quality Rollups," these hybrid updates are a combination of old and new, as in brand new, as in "preview" new. That label marks the update, which is generally distributed the third week of the month, almost always the third Tuesday, as one containing early looks at fixes that Microsoft has crafted for next month's non-security issues. Here's how the company defines preview quality updates: "The Preview of Monthly Rollup ... addresses new non-security updates and includes fixes from the latest Monthly Rollup." The non-security bug fixes bundled with the preview are those Microsoft intends to include in final form in the following month's Patch Tuesday rollup. The preview is also cumulative, in that it contains all previous monthly rollups for the targeted product, such as Windows 7. According to Microsoft, it offers the preview monthly rollups so customers can complete "early deployment of the new reliability fixes before they are included in the next Monthly Rollup" and give customers "visibility and testing of the planned non-security fixes targeted for the next month's Update Tuesday release." In plain English, the previews largely exist so that customers can help test the next month's non-security bug fixes, yet another example of the years-long trend of Microsoft shifting quality control testing to users. The previews, when labeled as such — including the "Preview of Monthly Quality Rollups" — are a Windows 7/8.1- and Windows Server 2008/2012-only term. It's not that Windows 10 doesn't serve previews to customers. It's just that Microsoft doesn't tag them with a clear nameplate. Instead, they're simply another cumulative update, albeit one released on the third or even fourth Tuesday of the month. Microsoft has referred to these Windows 10 updates as its "C" and "D" releases — to mark them as third- (as in C) and fourth-week (D) deliveries. Don't bother looking for the alphabetical markers or "Preview quality updates" in WSUS or Windows Update or the Update Catalog, however. And that's a problem. "Would it be possible to add the naming 'Preview' to these D week releases so that there is consistency between the Windows 7 update naming and Windows 10 for these D week releases?" asked one commenter in a Microsoft post of September 2018 that described Windows 10's update tempo. Microsoft has yet to address that reasonable request. Twice-yearly feature updates While the twice-annual updates that add new features and functionality to Windows 10 are the least frequently released of any of the five categories, ironically they're the sturdiest in definition. Few Windows 10 users question what they are: The regularly paced refreshes that replaced the once-every-three-years-or-so upgrade from one Windows OS to the next, a practice Microsoft pitched for decades. (Side note: Here at Computerworld, the term "feature upgrade" is often the substitute for Microsoft's "feature update." It's not that we're in the Windows dictionary business, but the twice-annual releases are more substantial and significant than the run-of-the-mill "update," and so should be marked as such. The term "upgrade" has long been that marker.) These are the updates identified with a four-digit number, as in 1809 or 1903, in the yymm format of their targeted completion date. On the client side, they are, as said, Windows 10-only; older versions of Windows — what Microsoft likes to call "down-level operating systems" — do not see these. But although there's little confusion about what a feature update is, there's plenty about almost everything else. Take this example: Last year, Microsoft split the two-times-a-year updates into two classes. Enterprises got 30 months of support for each year's fall update (12 months more than the standard 18 months). But Microsoft has yet to identify this new premier-class in the updates' naming. Why not? Source: The Windows update dictionary Microsoft never wrote (Computerworld - Gregg Keizer)
  10. Cauptain

    Visual Subst 2.0

    VISUAL SUBST 2 Map Virtual Drives Easily, Reduce Long Paths to Just One Letter with Visual Subst Visual Subst is a small tool that allows you to associate the most accessed directories with virtual drives. It solves three main issues with the built-in 'subst' command: it seamlessly creates drives for elevated applications, adds editable drive labels and restores drives after reboots. Also, Visual Subst makes it easier to create, edit and remove virtual drives in a GUI way. Features: Homepage: https://www.ntwind.com/software/visual-subst.html Download Page: https://www.ntwind.com/download/VSubst_2.0-setup.exe Medicine: waiting for a great soul
  11. Bitdefender 2019 - Stable - Final - Online/Offline Standalone Installers For Windows[x86 & x64] More Info/Official News: https://www.bitdefender.com/news/bitdefender-new-security-line-will-stop-most-sophisticated-attacks-3533.html BD 2019 Home/Home Office Forum: https://forum.bitdefender.com/index.php?/forum/536-bitdefender-2019-products/ BD TS 2019 Support: https://www.bitdefender.com/consumer/support/product/26925/ Improvements in BD 2019: https://www.bitdefender.com/consumer/support/answer/13353/ Changelog - gathered by Wortex/bitdefender forum: https://www.bitdefender.com/media/html/consumer/new/launch2019-opt/ Online Installers: Bitdefender Antivirus Plus 2019 Online: https://download.bitdefender.com/windows/installer/en-us/bitdefender_antivirus.exe XP | Vista: https://download.bitdefender.com/windows/installer/en-us/xp-vista/bitdefender_antivirus.exe Bitdefender Internet Security 2019 Online: https://download.bitdefender.com/windows/installer/en-us/bitdefender_isecurity.exe XP | Vista: https://download.bitdefender.com/windows/installer/en-us/xp-vista/bitdefender_isecurity.exe Bitdefender Total Security 2019 Online: https://download.bitdefender.com/windows/installer/en-us/bitdefender_tsecurity.exe XP | Vista: https://download.bitdefender.com/windows/installer/en-us/xp-vista/bitdefender_tsecurity.exe Offline Installers and Install Guide: Bitdefender 2019 Offline Installation Guide: Bitdefender 2019 AV Plus / Internet Security / Total Security - Standalone Installers [Windows]: 32bit [x86] - [Size: 428 MB]: https://download.bitdefender.com/windows/desktop/connect/cl/2019/all/bitdefender_ts_23_32b.exe 64bit [x64] - [Size: 456 MB]: https://download.bitdefender.com/windows/desktop/connect/cl/2019/all/bitdefender_ts_23_64b.exe Bitdefender Agent - 2019 - Universal [Same Agent for AV Plus / IS / TS]: Screenshots: Install Notes: Precaution Note: If you've already installed older version of Bitdefender[incl. 2016 version], we are sure that you'll lose your settings. Please take note of configuration, settings. whitelisted files and links. Also read the support page link above for upgrade/install Bitdefender 2019. Download and Install Bitdefender Agent. When it starts downloading the install files, Stop/Close it immediately. Note: Check whether there the Agent is installed only once in "Add/Remove Programs" or "Programs & Features". Note: Check in "Program Files" for folder named "Bitdefender Agent". Now, start installing offline installer and proceed with installation. Note: Please choose respective download link based on architecture x86/x64 for smooth installation. Note: Don't worry about AV Plus/IS/TS. The installer automatically modifies the installation depending on the license you entered. Once installation is done, configure accordingly for best protection and to avoid files from getting deleted. Configure Whitelist files and links if you have any. It is better to keep note of the configured settings for future use. User Guide: Bitdefender Antivirus Plus 2019: https://download.bitdefender.com/resources/media/materials/2019/userguides/en_EN/bitdefender_av_2019_userguide_en.pdf Bitdefender Internet Security 2019: https://download.bitdefender.com/resources/media/materials/2019/userguides/en_EN/bitdefender_is_2019_userguide_en.pdf Bitdefender Total Security 2019: https://download.bitdefender.com/resources/media/materials/2019/userguides/en_EN/bitdefender_ts_2019_userguide_en.pdf Uninstall Tool: Uninstall Tools Home: https://www.bitdefender.com/site/view/uninstall_consumer_paid.html Uninstall Tool For Bitdefender 2018 Products: https://www.bitdefender.com/files/KnowledgeBase/file/Bitdefender_2018_UninstallTool.exe NOTE: Bitdefender 2018 Uninstall Tool require KB2999226. If you didn't install, you'll get error "api-ms-win-crt-runtime-l1-1-0.dll" missing. You can download it here - KB2999226 Uninstall Tool For Bitdefender 2017 Products: http://www.bitdefender.com/files/KnowledgeBase/file/Bitdefender_2017_UninstallTool.exe NOTE: Bitdefender 2017 Uninstall Tool require KB2999226. If you didn't install, you'll get error "api-ms-win-crt-runtime-l1-1-0.dll" missing. You can download it here - KB2999226 Uninstall Tool For Bitdefender 2016 Products: http://www.bitdefender.com/files/KnowledgeBase/file/Bitdefender_2016_UninstallTool.exe Uninstall Tool For Bitdefender 2015 / 2014 / 2013 Products: http://www.bitdefender.com/files/KnowledgeBase/file/The_New_Bitdefender_UninstallTool.exe Uninstall Tool For Bitdefender 2012 Products and Earlier: http://www.bitdefender.com/files/KnowledgeBase/file/BitDefender_Uninstall_Tool.exe @[email protected] my revealed new ac extn method - modified as Jedi II 2018 TR tool by Jedi/Polylak work with 2019? If not, check TR release 2019. Thanks.
  12. If you're setting up a PC for others to use then you’ll often want to limit their actions, prevent them running other applications or tweaking system settings. Windows has many security and user settings that can help, but they're scattered across many applets and may be hard to find. FrontFace Lockdown Tool is a freeware application which gives convenient access to many of these settings, allowing you to heavily restrict your chosen account in just a few minutes. The program organizes its settings into three sections -- Startup and Shutdown, Continuous Operation, Protection and Security -- and each one has various lists and checkboxes covering its options. At its simplest, you might use the program to disable various Windows functions. You can prevent a user launching Task Manager, switching between user accounts, logging off or shutting down the PC, using the Windows or Ctrl+Alt+Del keypresses. Not enough? You can also set up your PC to log into a particular user account automatically, without displaying the login screen. Disable login override (holding down Shift when you boot to log in somewhere else) as well and it’s far more difficult for a user to bypass. Set a particular startup program and that should launch whenever your system boots. If you need more protection, change your PC’s shell to that application, instead of Explorer, and the usual Explorer shortcuts will no longer be available. Even if you stick with Explorer, there are ways to limit user actions, such as hiding any system tray icons on the Windows taskbar. It's also possible to shut down, hibernate or reboot the PC at a set time each day. If you’re building a kiosk PC this should help you keep any maintenance to a minimum. FrontFace Lockdown Tool doesn’t support the full set of Windows and Explorer user policies. You can’t hide particular drives, conceal selected Control Panel applets, stop users running REGEDIT and so on. The program does offer a simple way to create a kiosk-type system, though. It’s portable, so convenient to use, and a "restore default settings" button should get you out of trouble if you’ve made a mistake. Check it out. FrontFace Lockdown Tool is a freeware application for Windows 7 and later. Article source
  13. Although it’s much too early to draw any definitive conclusions, initial reports are that the March 2019 Patch Tuesday rollout hasn’t hit any major bumps. There are a few odd nuances, though, that warrant your consideration. Thinkstock/Microsoft Patch Tuesday has come and gone, not with a bang but a whimper. As of this moment, early Wednesday morning, I don’t see any glaring problems with the 124 patches covering 64 individually identified security holes. But the day is yet young. There are a few patches of note. Two zero days Microsoft says that two of this month’s security holes — CVE-2019-0797 and CVE-2019-0808 — are being actively exploited. The latter of these zero days is the one that was being used in conjunction with the Chrome exploit that caused such a kerfuffle last week, with Google urging Chrome browser users to update right away, or risk the slings of nation-state hackers. If you’ve already updated Chrome (which happens automatically for almost everybody), the immediate threat has been thwarted already. These two security holes are Elevation of Privilege bugs, which means that a miscreant who’s already gotten into your system can use the bugs to move up to admin status. So if you’re in charge of systems that are susceptible to sophisticated attacks, these patches warrant concern. For everybody else, they’re not the stuff of Stephen King class nightmares. As usual, Martin Brinkmann on ghacks.net has a thorough listing, the SANS ISC forum has a succinct chart, and Dustin Childs on the Zero Day Initiative blog offers many tech details. Win10 version 1809 oddities The Win10 version 1809 cumulative update, KB 4489899, fixes the “crazy” performance drop in some games, including Destiny 2, that we encountered two weeks ago. However, it doesn’t fix the other bug introduced by the “second February” 1809 cumulative update, KB 4482887, which clobbers audio settings in specific circumstances: After installing this update on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. As erpster4 notes on Tenforums: KB 4489899 causes that problem only if there are multiple audio outputs or playback devices for Realtek HD audio (speakers, realtek digital output [SPDIF], etc.) and the output selected is not the "default audio device." If only the "Speakers" output is listed on the Sound properties playback tab for Realtek audio (usually on ALC2xx codecs), then KB 449899 is safe to install. In addition, this month’s KB 4489899 doesn’t fix the MSXML 6 bug introduced by the first cumulative update in January: After installing this update, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode(). Makes you wonder if 1809 will get the "ready for business deployment" imprimatur before 1903 hits the skids. Er, goes out the chute. That's how it's supposed to work, yes? Servicing Stack Update for Win7 Here’s where the going gets a bit thick. As explained in November, Microsoft is changing the way it’s signing patches for Win7. Starting in July, your Win7 machine has to understand SHA-2 encryption in order to receive new patches. (Yes, this is the same Win7 that’ll no longer receive new security patches next January.) Microsoft released two SHA-2 related patches. KB 4490628 is a Servicing Stack Update — it fixes the part of Windows 7 that installs patches. KB 4474419 fixes Windows itself so it can handle SHA-2 encryption. As @DrBonzo explains, and @PKCano reiterates, if you’re manually installing Win7 patches, you need the Servicing Stack Update KB 4490628 before you install this month’s patches. (If you let Windows Update install the patches, it’ll get installed first.) Then the Windows-only fix KB 4474419 can follow along any time before July. If you’re installing the Win7 updates manually, there’s a specific installation sequence detailed by @PKCano that ensures the updates go in the correct order. Dearth of Office patches With all the love being showered on Windows 7 this week (including DirectX 12 for some games, and more annoying “Get Windows 10” nag screens), you might expect more sweetness and light for Office apps. Not so. We only have six new Office security patches, to add to the 28 non-security patches from earlier this month: one for Office 2010 and five for various Server versions. Remarkably, there are no new security patches for Office 2013 or 2016, although we do have two new versions of Office Click-toRun: 15.0.5119.1000 for Office 2013; 14.0.7230.5000 for Office 2010. Thanks to @PKCano, @DrBonz, @abbodi86 and many others who volunteer their help keeping the patching gremlins at bay. Questions? Problems? Hit us on the AskWoody Lounge. Source: March 2019 Windows and Office patches poke a few interesting places (Computerworld - Woody Leonhard)
  14. Easy editing - PowerDirector can help you easily make a movie. One-click color correction is the unique new feature that can help your video clips to be true-to-life appearance Precision video editing features - PowerDirector 17 optimizes 8 customizable design tools, Plus Chroma Key editing, frame-by-frame motion tracking and video collages & multicam editing Professional grade features & performance - PowerDirector has held the title of world's fastest video editing software for several versions, and supports 4K and 2K Ultra video formats Plug-ins & effects - power Director includes cyberlink's unique creative design packs and professional 3rd party plug-ins from world-renowned sources such as newbluefx, ProDAD and Boris FX Step-by-step tutorials - novice and experienced users alike can find step-by-step guides, videos and tutorials explaining how to get the most from powerdirector's wide array of features Site: https://mega.nz Sharecode: /#!0lw1jCBb!WHlni9Zp-Y5OvUsy3rTsrgr3BYAgupVTPtL_2VfjCUA Site: https://dailyuploads.net Sharecode: /c1f1ffum56s2 Site: https://userscloud.com Sharecode: /8d434leiqq3s Site: http://uppit.com Sharecode: /2s0hb3amqqza
  15. With a few lingering holes plugged in the past couple of days, it looks like the coast is clear for applying the February 2019 Windows, Office and Net patches. But there are some troubling reports of bluescreens with the Win 8.1 Monthly Rollup. Franck V. (CC0) Microsoft’s February patches have been relatively benign, for all except those running Windows 8.1. Since I wrote about the outstanding problems last week, we’ve had a few interesting new developments: Microsoft released the second February cumulative update for Windows 10 version 1809, KB 4482887. It has three dozen bug fixes, including a fix for the Access95-era Jet database bug, but appears to be quite solid. There’s a mysterious new “Compatibility update for upgrading to and recovering Windows 10, version 1809: March 1, 2019” KB 4489491 that’s so poorly documented it could do just about anything. I often wonder how admins with regulatory responsibilities can install stuff like this. The “Access 95 Jet database bug” introduced by this month’s Win7 and 8.1 Monthly Rollups and Security-only patches now have standalone fixes in the Microsoft Catalog -- KB 4490511 for Win7 and KB 4490512 for Win8.1. I’m seeing reports of bluescreens after installing this month’s Win 8.1 Monthly Rollup, KB 4487000. If you’re using Windows 8.1, you should be prepared to roll back the Monthly Rollup. All of this comes in addition to the “Internet Explorer doesn’t understand the backslash” bug I described last week. @PKCano further admonishes, “Watch out for the KB 4491113 hotfix Cumulative update for IE 11, which can cause additional problems. Unless you are having that specific problem – and you can’t avoid using IE 11 – avoid the fix.” Susan Bradley’s detailed Master Patch List shows that we’re ready to go – even with this month’s NET patches. Win10 1809 rolling out slowly, slowly If you have any version of Win10, you’re in the crosshairs for Microsoft’s latest version pushed with the help of a new, improved, extraterrestrial superintelligent next-generation machine-learning model. People ask me why I’m so cynical about 1809. I’m not really all that cynical – in fact, it looks like Microsoft’s trying very hard to make this one better than all that came before. My skepticism stems from the fact that 1809 doesn’t bring anything I want to the table: A new clipboard that’s almost as good as decade-old free plugins; better screenshots with markup; Storage Sense improvements that are disabled by default for good reason; and a handful of ho-hum features. Should you upgrade your machine for that? Bottom line remains the same: Unless you want Win10 version 1809 on your machine, you need to proactively block it until you’re comfortable with moving on to the next, arguably better version of the last version of Windows. Update how-to Here’s how to get your system updated the (relatively) safe way. Step 1. Make a full system image backup before you install the February patches. There’s a non-zero chance that the patches — even the latest, greatest patches of patches of patches — will hose your machine. Best to have a backup that you can reinstall even if your machine refuses to boot. This is in addition to the usual need for System Restore points. There are plenty of full-image backup products, including at least two good free ones: Macrium Reflect Free and EaseUS Todo Backup. For Win 7 users, If you aren’t making backups regularly, take a look at this thread started by Cybertooth for details. You have good options, both free and not-so-free. Step 2. For Win7 and 8.1: Microsoft is blocking updates to Windows 7 and 8.1 on recent computers. If you are running Windows 7 or 8.1 on a PC that’s 18 months old or newer, follow the instructions in AKB 2000006 or @MrBrian’s summary of @radosuaf’s method to make sure you can use Windows Update to get updates applied. If you’re very concerned about Microsoft’s snooping on you and want to install just security patches, realize that the privacy path’s getting more difficult. The old “Group B” — security patches only — isn’t dead, but it’s no longer within the grasp of typical Windows customers. If you insist on manually installing security patches only, follow the instructions in @PKCano’s AKB 2000003 and be aware of @MrBrian’s recommendations for hiding any unwanted patches. For most Windows 7 and 8.1 users, I recommend following AKB 2000004: How to apply the Win7 and 8.1 Monthly Rollups. Realize that some or all of the expected patches for February may not show up or, if they do show up, may not be checked. DON'T CHECK any unchecked patches. Unless you're very sure of yourself, DON'T GO LOOKING for additional patches. In particular, if you install the February Monthly Rollups or Cumulative Updates, you won’t need (and probably won’t see) the concomitant patches for January. Don't mess with Mother Microsoft. Watch out for driver updates — you’re far better off getting them from a manufacturer’s website. After you’ve installed the latest Monthly Rollup, if you’re intent on minimizing Microsoft’s snooping, run through the steps in AKB 2000007: Turning off the worst Win7 and 8.1 snooping. If you want to thoroughly cut out the telemetry, see @abbodi86’s detailed instructions in AKB 2000012: How To Neutralize Telemetry and Sustain Windows 7 and 8.1 Monthly Rollup Model. Realize that we don’t know what information Microsoft collects on Window 7 and 8.1 machines. But I’m starting to believe that information pushed to Microsoft’s servers for Win7 owners is almost as extensive as that pushed in Win10. Step 3. For Windows 10: If you’re running Win10 version 1709, or version 1803 (my current preference), you definitely want to block the forced upgrade to Win10 1809. Don’t get caught flat-footed: Microsoft is pushing 1809 slowly, but you don’t have to go when that superintelligent deployment program says you’re ready. Follow the advice in How to block the Windows 10 October 2018 Update, version 1809, from installing. Of course, all bets are off if Microsoft, uh, forgets to honor its own settings. Those who run Win10 Pro/Education and followed my advice in February – to set “quality update” (cumulative update) deferrals to 15 days, per the screenshot – don’t need to do anything. Your machine already updated itself on the 27th. Don’t touch a thing and in particular don’t click Check for updates. Woody Leonhard For the rest of you, including those stuck with Win10 Home, go through the steps in "8 steps to install Windows 10 patches like a pro." Make sure that you run Step 3, to hide any updates you don’t want (such as the Win10 1809 upgrade or any driver updates for non-Microsoft hardware) before proceeding. If you really want to hide everything, including the mysterious KB 4023057 patch I mentioned last week, you need to go through @PKCano’s steps to wring every last update out of your update queue. Microsoft hides some of them. Thanks to the dozens of volunteers on AskWoody who contribute mightily, especially @sb, @PKCano, @abbodi86, and many others. We’ve moved to MS-DEFCON 4 on the AskWoody Lounge. Source: February's Windows and Office patches look ripe, but look out for Win 8.1 (Computerworld - Woody Leonhard)
  16. Screenshot: Changelog: Patch changed to offline patch only. no online servers for this patch. Links: ProPresenter Homepage: http://www.renewedvision.com/propresenter.php Download Page: http://www.renewedvision.com/pro_download.php Instructions: Download the bundle above, extract using WinRAR or 7zip Install ProPresenter 6 , but DO NOT launch ProPresenter 6 after install. Run Patch as Administrator Run the local webserver by running launch.bat The webserver is required for activation to work Run ProPresenter Updating your ProPresenter to the latest version: Each version will have a separate thread, as it is not encouraged here to edit threads. Modules: Modules are pre-registered with the patch. Use them in the preferences pane. DO NOT CLICK demo modules or buy. Bibles: To Install Bibles: Click the Bibles Icon on the ProPresenter Toolbar Click the GEAR icon on the Bibles Window Click the Bibles Tab Click the Free Bibles Tab Install the bible you need. Local webserver must be running if the Offline Patch is made, otherwise patch the program to download from the web. ProPresenter version 6 for Mac SEE Kataklop's Thread on MacSerialJunkie (google is your friend) He regularly updates as the Mac version also updates. His links are being removed by RenewedVision and maybe mine would be gone too Good luck getting the patch for new versions Blame those guys who post contents of this forum elsewhere.
  17. Patch Tuesday’s tomorrow, which means today offers an excellent opportunity to make sure your machine is braced for impact. Here’s your step-by-step guide to blocking patches as they come out the chute, so you can install them according to your schedule, not Microsoft's. Thinkstock Those of you who feel it’s important to install Windows and Office patches the moment they come out – I salute you. The Windows world needs more cannon fodder. When the bugs come out, as they inevitably will, I hope you’ll drop by AskWoody.com and tell us all about them. For those who feel that, given Microsoft’s track record of pernicious patches, a bit of reticence is in order, I have some good news. Microsoft’s Security Response Center says that only a tiny percentage of patched security holes get exploited within 30 days of the patch becoming available. Yes, it’s possible that you’ll be among the unlucky few. But in my experience, if you steer clear of Internet Explorer and Edge, and avoid hideously buggy packages like Adobe Flash and Reader, you’re much better off waiting a couple of weeks before applying the latest patches. Of course, you have to patch sooner or later. In some rare cases, you need to install specific patches shortly after they’re released. We’ll warn you about the stinkers. But in almost all cases, you can afford to wait a couple of weeks to get patches installed – and that’s usually enough time for the bad bugs to show themselves. Blocking automatic update on Win7 and 8.1 It’s true. Windows 7 originally shipped with an automatic update feature that was turned off by default. How times change, eh? If you’re using Windows 7 or 8.1, click Start > Control Panel > System and Security. Under Windows Update, click the "Turn automatic updating on or off" link. Click the "Change Settings" link on the left. Verify that you have Important Updates set to "Never check for updates (not recommended)" and click OK. Blocking automatic update on Windows 10 Pro If you’re using Windows 10 Pro version 1709, 1803, or 1809, I recommend an update blocking technique that Microsoft lists for “Broad Release” in its obscure Build deployment rings for Windows 10 updates -- which is intended for admins, but applies to you, too. (Thx, @zero2dash) Step 1. Using an administrative account, click Start > Settings > Update & Security. Step 2. On the left, choose Windows Update. On the right, click the link for Advanced options. You see the settings in the screenshot. Woody Leonhard Step 3. To pull yourself out of beta testing, in the first box, choose Semi-Annual Channel. ("Semi-Annual Channel" is this month's bafflegab version of the old "Current Branch for Business," which was a euphemism for "ready for paying customers.") Step 4. To further delay new versions until they’ve been minimally tested, set the “feature update” deferral setting to 120 days or more. That tells the Windows Updater (unless Microsoft makes another “mistake,” as it has numerous times in the past) that it should wait until 120 days after a new version is declared ready for broad deployment before upgrading and re-installing Windows on your machine. That has the added benefit of blocking Microsoft’s forced upgrade to Win10 version 1809, if you're on 1703 or 1709. You should choose when you want to upgrade. Don’t leave it up to Microsoft’s “next generation advanced learning” algorithm which, presumably, is more advanced than the current-generation advanced learning algorithm. Step 5. To delay cumulative updates, set the “quality update” deferral to 15 days or so. (“Quality update” = bug fix.) In my experience, Microsoft usually yanks bad Win10 cumulative updates within a couple of weeks of their initial release. By setting this to 10 or 15 or 20 days, Win10 will update itself after the major screams of pain have subsided and (with some luck) the bad cumulative updates have been pulled or re-issued. Step 6. Just “X” out of the settings pane. You don’t need to explicitly save anything. Step 7. Don’t click Check for updates. Ever. If there are any real howlers – months where the cumulative updates were irretrievably bad, and never got any better, as they were in July of last year – we’ll let you know, loud and clear. Tired old approach for Windows 10 Home Here’s the thing about Windows 10 Home. Microsoft considers Home customers fair game. They really should call it Win10 Guinea Pig edition. Microsoft has no qualms whatsoever in pushing its new, untested (perhaps I should say “less-than-thoroughly-tested”) updates and upgrades onto Windows 10 Home machines. This isn’t a mistake or an oversight. Win10 Home customers by design are Microsoft’s extended beta-plus testing force. Cannon fodder. It’s been that way since day one. As Susan Bradley says, “Every version of Windows should be able to defer and pause updates…. Microsoft, your customers deserve better than this.” If upgrading to Win10 Pro isn’t an option – and I sympathize if you’d rather not hand over another $100 to Microsoft for something that should come standard – your only other reasonable option is to set your internet connection to “metered.” Metered connections are an update-blocking kludge that seems to work to fend off cumulative updates, but as best I can tell still doesn’t have Microsoft’s official endorsement as a cumulative update prophylactic. To set your Ethernet connection as metered: Click Start > Settings > Network & Internet. On the left, choose Ethernet. On the right, click on your Ethernet connection. Then move the slider for Metered connection to On. To set your Wi-Fi connection as metered: Click Start > Settings > Network & Internet. On the left, choose Wi-Fi. On the right, click on your Wi-Fi connection. Move the slider for Metered connection to On. If you set your internet connection to metered, you need to watch closely as the month unfolds, and judge when it’s safe to let the demons in the door. At that point, turn “metered” off, and just let your machine update itself. Don’t click Check for updates. The current beta test version of the next (“19H1” or “1903”) version of Win10 Home includes the ability to Pause updates for seven days. While that’s certainly a step in the right direction, it doesn’t help much in the real world: You can only Pause once, and only for seven days You can’t Pause again without accepting all backed-up updates in the interim You have to know in advance that a bad update is coming down the pike – there’s no warning All of which makes Win10 Home “Pause updates” a really nifty marketing setting (“Look! You can pause updates in Win10 Home!”) that’s basically useless. Unless you’re Carnac the Magnificent. We’re at MS-DEFCON 2 on AskWoody. Source: News Analysis: It's time to block Windows Automatic Updating (Computerworld - Woody Leonhard)
  18. It’s a combination of things, but mostly it’s a shift in focus. Thinkstock Sometime this spring, Windows 10 will get its next update, which has become a twice-a-year ritual. Several years ago, Microsoft decided Windows 10 would be the last big-bang update for the operating system, as the company moved the OS to a Windows-as-a-service model. There’s no longer any need to buy a new version of Windows. It gets updated twice a year (and at no charge, since Windows as a service is not a subscription model), with security updates and bug fixes sandwiched in between. That’s certainly easy on the pocketbook. And it makes getting the latest and greatest version of the operating system easy as well. No need for ugly, messy, disk-based upgrades. It happens automatically over the internet. There’s only one problem with that approach: There haven’t been any “latest and greatest” features introduced into Windows for quite some time. And don’t be surprised if there never will be again. Under Windows as a service, the operating system gets more stable over time and patched more quickly. But the days of looking forward to something new and exciting in Windows are long gone. What you see today is essentially what you get tomorrow. I’ll explain why. First, let’s take a look at just at how ho-hum the last three of Windows 10’s updates have been and how few interesting features will be introduced in the next one. The Windows 10 Fall Creators Update, released in October 2017, tweaked OneDrive, introduced a moderately useful feature called My People that made it a bit easier to communicate with a few selected contacts, and failed miserably at trying to link Windows to Android and iOS phones. The next one, the Windows 10 April 2018 Update, introduced one interesting new feature, Timeline, that lets you resume your previous activities, but it’s somewhat crippled because it works with only a handful of select, Microsoft-created applications. The best feature of the most recent update, the Windows 10 October 2018 Update, was the moderately useful, powered-up Windows Clipboard. But given that a similar feature had been part of Windows more than three decades ago in Windows 1.0, and later killed, it’s not exactly a new idea. As for the next semiannual upgrade, due out this spring, don’t expect much. The preview builds have so far been underwhelming, including a tweaked Start menu, a new “Light” colour theme, and the ability to pause updates for a limited amount of time. Are you popping the champagne corks yet? I didn’t think so. Is Microsoft not working on anything for Windows that we might call major? Well, back in 2017, it announced that it was bringing a truly innovative feature to Windows 10 called Sets. Sets would put tabs into applications, not just browsers, and let you create documents that would combine multiple apps — for example, a Word document that had browser tabs on it for accessing any online research you’ve done. But announcing a killer feature is one thing, and delivering it is another thing entirely. And Microsoft has included the Sets feature in multiple previews of its twice-annual Windows updates, only to later pull it before release because Microsoft couldn’t get it to work properly. It won’t be in this spring’s update, either. Don’t be surprised if it never makes it into Windows 10. Why is this happening? One commentator, on Ars Technica, faults the process that Microsoft uses to develop Windows. He points out that Windows has a massive, complicated codebase, some of it ancient by tech standards. Before the Windows-as-a-service days, new versions of Windows were released every two to three years. That gave the company more time to develop and test new features. With twice-annual updates, the development process has been compressed into as little as one-sixth the time previously available. That makes it far more difficult to introduce significant new features that are bug-free. That’s true. But it’s not the primary reason there may never be a killer feature introduced into Windows. The real reason has more to do with business than with the development process. Microsoft CEO Satya Nadella has made a concerted effort to move Windows away from the core of the company’s business. He’s moved Microsoft’s focus toward the cloud and is also making sure Microsoft’s products are more open and work with other technologies, including open source, iOS and Android. That means more development time is spent on those capabilities than on introducing new Windows features. It’s worked spectacularly, with a resurgent Microsoft at times topping the list of the world’s most valuable public companies. So expect Windows to continue to become more reliable and stable over time, as it has been getting under the Windows-as-a-service strategy. And expect useful tweaks here and there. But don’t look for any new killer features. Under Microsoft’s successful pivot to the cloud, there’s no reason to develop and release them. Source: Why Windows may never get another killer feature (Computerworld - Preston Gralla)
  19. There are some rather obscure issues, but by and large, now’s a very good time to get Windows and Office caught up on patching. If you want to avoid Win10 1809 for now, block it. Watch out for the, uh, edge cases, and patch away. Thinkstock/Microsoft Compared to some months last year, January has been a Microsoft patching cakewalk. We had several rounds of close calls and missed calls, as I posted earlier this week, but almost everything is cleared up. We’ve seen a few more problems raise their ugly heads in the past few days: Microsoft has confirmed that the latest version of Office Click-to-Run (which you’re likely using if you have Office 365) makes the conversation window disappear in Skype for Business 2016. The Windows 8.1 Monthly Rollup, KB 4480963, breaks the Live Migration feature on older AMD Opteron machines. We’re still waiting for confirmation on that one. Citrix confirms (but Microsoft hasn’t acknowledged) that the latest Win10 1803 cumulative update, KB 4480976, causes page file problems when the page file isn’t sitting on C:. More details on Tenforums. Those are typical Microsoft edge-use bugs: They don’t affect many people, but if you’re one of the stuckees, you’re up the ol’ creek. There’s an additional, ongoing problem that deserves repeating for you Windows 7 customers who are sharing files on home networks. Both KB 4480970, the January Monthly Rollup, and KB 4480960, the Security-only patch, have a bug that can break your network. The only solution is to manually install a Silver Bullet patch, KB 4487345 — and that doesn’t always work. Details in my Patch Alert article. Win10 1809 rolling out slowly, slowly If you have any version of Win10, you’re in the crosshairs for Microsoft’s latest version pushed with the help of a new, improved, extraterrestrial superintelligent next-generation machine-learning model. People ask me why I’m so cynical about 1809. I’m not really all that cynical — in fact, it looks like Microsoft’s trying very hard to make this one better than all that came before. My skepticism stems from the fact that 1809 doesn’t bring to the table anything I want: A new clipboard that’s almost as good as decade-old free plugins; better screenshots with markup; Storage Sense improvements that are disabled by default for good reason; and a handful of ho-hum features. Should you upgrade your machine for that? Bottom line remains the same: Unless you want Win10 version 1809 on your machine, you need to proactively block it until you’re comfortable with moving on to the next, arguably better version of the last version of Windows. Update Here’s how to get your system updated the (relatively) safe way. Step 1. Make a full system image backup before you install the January patches. There’s a non-zero chance that the patches — even the latest, greatest patches of patches of patches — will hose your machine. Best to have a backup that you can reinstall even if your machine refuses to boot. This, in addition to the usual need for System Restore points. There are plenty of full-image backup products, including at least two good free ones: Macrium Reflect Free and EaseUS Todo Backup. For Win 7 users, If you aren’t making backups regularly, take a look at this thread started by Cybertooth for details. You have good options, both free and not-so-free. Step 2. For Win7 and 8.1 Microsoft is blocking updates to Windows 7 and 8.1 on recent computers. If you are running Windows 7 or 8.1 on a PC that’s 18 months old or newer, follow the instructions in AKB 2000006 or @MrBrian’s summary of @radosuaf’s method to make sure you can use Windows Update to get updates applied. If you’re very concerned about Microsoft’s snooping on you and want to install just security patches, realize that the privacy path’s getting more difficult. The old “Group B” — security patches only — isn’t dead, but it’s no longer within the grasp of typical Windows customers. If you insist on manually installing security patches only, follow the instructions in @PKCano’s AKB 2000003 and be aware of @MrBrian’s recommendations for hiding any unwanted patches. For most Windows 7 and 8.1 users, I recommend following AKB 2000004: How to apply the Win7 and 8.1 Monthly Rollups. Realize that some or all of the expected patches for December may not show up or, if they do show up, may not be checked. DON'T CHECK any unchecked patches. Unless you're very sure of yourself, DON'T GO LOOKING for additional patches. In particular, if you install the January Monthly Rollups or Cumulative Updates, you won’t need (and probably won’t see) the concomitant patches for December. Don't mess with Mother Microsoft. Watch out for driver updates — you’re far better off getting them from a manufacturer’s website. After you’ve installed the latest Monthly Rollup, if you’re intent on minimizing Microsoft’s snooping, run through the steps in AKB 2000007: Turning off the worst Win7 and 8.1 snooping. If you want to thoroughly cut out the telemetry, see @abbodi86’s detailed instructions in AKB 2000012: How To Neutralize Telemetry and Sustain Windows 7 and 8.1 Monthly Rollup Model. Realize that we don’t know what information Microsoft collects on Window 7 and 8.1 machines. But I’m starting to believe that information pushed to Microsoft’s servers for Win7 owners is nearing equality to that pushed in Win10. Step 3. For Windows 10 If you’re running Win10 version 1709, or version 1803 (my current preference), you definitely want to block the forced upgrade to Win10 1809. Don’t get caught flat-footed: Microsoft is pushing 1809 slowly, but you don’t have to go when that superintelligent deployment program says you’re ready. Follow the advice in How to block the Windows 10 October 2018 Update, version 1809, from installing. Of course, all bets are off if Microsoft, uh, forgets to honor its own settings. Those of you who run Win10 Pro/Education and followed my advice in November — to set “quality update” (cumulative update) deferrals to 15 days, per the screenshot — don’t need to do anything. Your machine already updated itself on the 23rd. Don’t touch a thing and in particular don’t click "Check for Updates." Woody Leonhard For the rest of you, including those of you stuck with Win10 Home, go through the steps in "8 steps to install Windows 10 patches like a pro." Make sure that you run Step 3, to hide any updates you don’t want (such the Win10 1809 upgrade or any driver updates for non-Microsoft hardware) before proceeding. If you really want to hide everything, including the gonzo KB 4023057 patch I mentioned earlier this week, you need to go through @PKCano’s steps to wring every last update out of your update queue. Microsoft hides some of them. This month make sure you’re the windshield, not the bug. Thanks to the dozens of volunteers on AskWoody who contribute mightily, especially @sb, @PKCano, @abbodi86, and many others. We’ve moved to MS-DEFCON 4 on the AskWoody Lounge. Source: The January Windows and Office patches are good to go (Computerworld - Woody Leonhard)
  20. Patches are crawling out of the woodwork, and bugs follow as night unto day. Be particularly cautious if you’re running a turn-of-the-century database application; and if you don’t want to be forced to Win10 1809, get your shields up. Thinkstock/Microsoft In general, the January patches look relatively benign, but for some folks in some situations they can bite. Hard. On the surface we’ve seen the usual Patch Tuesday Cumulative Updates and secondary Cumulative Updates for all versions of Windows 10. Microsoft calls the secondary Cumulative Updates “optional” because you only get them if you click “Check for updates.” Windows 7 and 8.1 got their usual Monthly Rollups, but there’s a problem. Specifically, this month’s Win7 Monthly Rollup has a couple of bugs that are only fixed if you install the preview of February’s Monthly Rollup. Which makes no sense at all, but that’s Microsoft. There’s another Win7 Monthly Rollup bug that’s fixed by installing a different “silver bullet” patch. A Win10 version 1809 .NET patch, KB 4481031, rolled out as a Preview when it wasn’t. Some folks woke up one morning to a notification that their PC was no longer activated. That was a bug on Microsoft’s side. Oops. Office 2010 took one on the chin. Two, actually. And it looks like the Japanese calendar problem’s still there, with “fixes” bringing Word, Excel and Access to a halt. And then there’s a reprisal of the mysterious KB 4023057 “update reliability” patch, throwing error 0x80070643 on some machines. It’s been a patch pokin’ month. Windows 10 All of the extant versions of Windows 10 got Patch Tuesday cumulative updates this month, and then the usual second round of cumulative updates. The former came down the Automatic Update chute; the latter lie in wait unless you click “Check for updates.” That’s been the common, infuriating, behavior for several months. Nothing new. What isnew is the remarkable delay in releasing the second patch for Win10 version 1809 – the KB 4476976 “October 2019 Update.” Microsoft held onto that patch for an extra week, putting it through an unusual second round of beta tests in the Windows Insider Preview Ring. That’s great news: It shows Microsoft’s taking its time to push out the 1809 updates. It remains to be seen if the new-found restraint will result in less-buggy patches, but slowing down the gauntlet certainly rates as a step in the right direction. The two major bugs in all of this month’s Win10 patches are the acknowledged ones: Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”. After installing KB4480966, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive. The first bug strikes (old!) applications written in Access 97 and in other database packages. There’s a manual solution, but it isn’t pretty, and it requires you to convert the database to a newer format. That’s not welcome news to anyone who’s nursing an old database. The second bug has a simple workaround: Don’t use Edge. As if you needed me to tell you that. Win10 version 1809 .NET patch KB 4481031 This was yet another Keystone Kops patch. Microsoft originally released KB 4481031 with a KB article that said it was a “Preview of Cumulative Update.” It was actually a real patch. Microsoft pushed KB 4481031 out the Windows Update chute. That, we were told two days later, was a mistake. Right now, I’m told, KB 4481031 is a for-real cumulative update that’s only being pushed to people who click “Check for updates.” Windows 7 and 8.1 I don’t believe the conspiracy theories – that Microsoft’s intentionally planting bugs in Win7 patches to prod people on to Win10. But I do believe the complacency theories – that Microsoft’s focusing on Win10 efforts to the detriment of Win7 users, in particular. This month we saw two big bugs introduced in the Win7 Monthly Rollup, along with the Access 97 file format problem in Win10: Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the Jan. 8 security updates. This does not affect domain accounts in the local "Administrators" group. Some programs don’t display F1 Help correctly. The first problem is pretty specific: You have to be running a peer-to-peer network, and the person trying to get to the shared folders has to have an administrator account on the shared folder’s PC. Microsoft released a “Silver Bullet” patch for this specific problem, KB 4487345. Susan Bradley has a more detailed explanation – and advice if KB 4487345 doesn’t work – in her Patch Watch column. The second problem (which isn’t acknowledged in the Monthly Rollup KB article) can be fixed by installing the preview of next month’sWin7 Monthly Rollup, KB 4480955. There’s an additional problem. Installing KB 4480970 (this month’s Monthly Rollup) or KB 4480960 (security-only) breaks RDP on Server 2008 R2 systems. It looks like installing the Silver Bullet patch KB 4487345 also fixes this problem. Patch Tuesday also brought an embarrassing barrage of activation failures and “Not genuine” / ”counterfeit copy of Windows” notifications on Win7 machines with volume licenses. Microsoft has confirmed that the problem isn’t with this month’s update, it’s with Microsoft’s activation servers. Which have since been fixed. Supposedly. Windows 8.1 continues its admirable stretch as the most stable version of Windows yet. KB 4023057 reappears Now in its 50th-or-so incarnation, KB 4023057, the “update reliability improvement” rolled out to Win10 1507, 1511, 1607, 1703, 1709 and 1803 machines. Microsoft still hasn’t said what KB 4023057 actually does, the KB article is a baffling bit of bull… pablum. Speculation is that KB 4023057 blasts away any impediments you’ve set to the automatic installer. @ch100 on AskWoody has offered the only explanation that makes sense to me: KB4023057 was and still is one of the most weird and unexplained updates in the recent times. This update has never been offered to WSUS, but only to Windows Update. This would indicate that it [was] meant for unmanaged end-users and unmanaged small business users… This patch may be harmless, but why it was released and where it actually applies, it is still a mystery. More Office 2010 messes Patch Tuesday also brought KB 4461614, an Office 2010 security update. Unfortunately, as soon as you install that patch, Access and Excel stop working. Ten days later, Microsoft issued a replacement, KB 4462157. Now we have notices that KB 4462157 breaks Office 2010 entirely on Windows XP machines. Pro tip: If you’re still running XP, you have worse things to worry about. We’ll keep you posted on patches on the AskWoody Lounge. Source: Microsoft Patch Alert: January patches include a reprisal of KB 4023057 and a swarm of lesser bugs (Computerworld - Woody Leonhard)
  21. Dr.Web Security Space is an advanced security application that comes packed with several protection modules for fighting against all sorts of threats that may comprise your computer’s stability and performance. It offers support for antivirus, protection against spam and phishing websites, parental control, remote antivirus network options, firewall (you may choose to deploy it on your PC during the installation process), identification of malicious URLs via its personal cloud servers, backups, and blocking mode for removable devices. Some of the most notable antivirus technologies offered by Dr.Web Security Space help you detect viruses, malware, and other types of threats in real time, automatically update virus definitions, proactively block viruses, as well as discover spam emails and filter messages in real time. Dr.Web Security Space for Windows for 3 months Dr.Web Anti-virus for MacOS for 3 months Dr.Web Anti-virus for Linux for 3 months Giveaway: link https://www.comss.ru/page.php?id=5299 Obtaining a license for 3 months 1. To use Dr.Web Antivirus free 3 months, go to the respective product download page: https://www.comss.ru/download/page.php?id=5299 2. On the product page, click Download for 3 months and enter your email address. 3. Confirm your email address after receiving the letter and complete the registration for demolitsenzii Dr.Web for 3 months. conditions proposals You get a trial version (demolitsenziyu) for 3 months free of charge (demoperiod). Validity demolitsenzii starts with the activation code received. Free use of the software Dr.Web for demoperioda guaranteed only if the user agrees to receive service messages about the status of the license. In the case of non-receipt of these messages demolitsenziya blocked, and the following license for examination can be received only nine months after the opt-out
  22. The following guide demonstrates how to disable auto suggest functionality in Windows Explorer (File Explorer) and the Run box on Windows devices. When you type something in Explorer's location field, suggestions are displayed based on certain factors, e.g. if a file of that name is found on the desktop. The same happens when you launch the run box on Windows using Windows-R when you use it to run commands. Some users may like the functionality as it makes it easy to select one of the suggested options to save time; others may dislike it for a number of reasons such as never using these suggestions and disliking the fact that the suggest menu hides some of the content in Explorer. Windows administrators have two options to deal with the issue: Make a change in the Windows Registry to turn suggestions off. Use the Internet Options to do that instead. Using the Windows Registry You can turn off suggestions in Explorer and the Run box in the Registry. Note that you need elevated rights to make changes to the Registry. Open the Start Menu on the Windows device. Type regedit and select the result. Confirm the UAC prompt that is displayed. Go to Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\AutoComplete Note: if AutoComplete does not exist, right-click on Explorer and select New > Key. Name it AutoComplete. Right-click on AutoComplete and select New > String Value. Name the String AutoSuggest. Double-click on AutoSuggest and change the value to no. Restart the PC. Tip: if you don't need the auto-complete feature create another String under AutoComplete. Name it Append Completion (with a space), and set it to no as well. Using the Internet Properties If you don't want to make changes to the Registry, you may make the change in the Internet Options as well. Open the Start Menu on the Windows PC or use Windows-R to open the run box. Type inetcpl.cpl and hit return to open the Internet Options. Tip: check out our handy guide on opening Control Panel modules quickly using shortcuts. Windows 10: Switch to the Advanced tab. Scroll down until you find "Use inline AutoComplete in File Explorer and Run Dialog". Click ok. Windows 7: Switch to the Content tab. Activate Settings next to AutoComplete. Remove the checkmark from "Address bar". Click ok. Close the Internet Options. Closing words There does not seem to be a way to disable suggestions in just one application and not the other. Source: How to disable Auto Suggest in Explorer and Run Box on Windows (gHacks - Martin Brinkmann)
  23. Wale, which stands for Windows Audio Loudness Equalizer, is a free open source software program for Windows to normalize Windows audio levels. Did you ever run into audio playback issues that caused the volume of audio to be too loud in application and not nearly loud enough in another? Or audio issues on the same site when you play different videos? While you can use the volume slider on websites, the native volume controls for applications that Windows provides to change the audio level or speaker volume controls, having to do so regularly is not overly comfortable. Windows Audio Loudness Equalizer attempts to fix the issue by adjusting audio playback while it is active on the Windows PC. Windows Audio Loudness Equalizer The program interface looks intimidating at first, and even more so if you are not familiar with certain audio-related terms. Note: Windows may throw a smartscreen warning when you try to install the program on the Windows PC. A scan on Virustotal came up negative except for one antivirus engine that reported a hit (Qihoo-360). A portable version is also available. Wale adds an icon to the system tray area that you need to interact with to configure it. A double-click opens the main interface which is divided into the three tabs View, Config, and Log. View displays information about running processes that play audio for the most part and some general audio related information. You may want to switch to Config on first start to configure base parameters; some of these may intimidate you even further but it is just a matter of trial and error to get the configuration right. The program has a "return to default" button to restore the program defaults. What you may want to do is verify that the base level is set correct. Volume will be louder if you increase the base level and quieter if you decrease it. You will notice that Wale adjusts the volume of application's that play audio automatically. The volume slider may adjust itself multiple times or even all the time to find the right playback level for audio. Wale supports a handful of additional configuration options: you may use them to set the process priority, update intervals and other variables. Closing Words and verdict Windows Audio Loudness Equalizer attempts to keep the volume of any audio playing on the Windows device it runs on in user defined levels. If you encounter too loud or too quiet audio often, even while using a single application, you may want to give it a try to improve your experience. Source: Different audio playback volumes annoy you? Wale for Windows fixes that (gHacks - Martin Brinkmann)
  24. Microsoft released KB4481031, a cumulative update for the .NET Framework 3.5 and 4.7.2 for Windows 10 version 1809 and Windows Server 2019 on January 22, 2019. Several things were odd about the release: The patch was labeled as a preview, and it was available if users clicked on the "check for updates" button manually but also automatically through Windows Update. Some administrators thought that Microsoft made an error in the documentation of the update -- which happened in the past -- while others that someone at Microsoft pushed the wrong button, again, to push an update to devices run by admins who were not seeking for it actively. There is a reason why it is recommended to never hit the "check for updates" button manually on a device running Windows; it may push preview updates to stable versions of Windows or new feature updates that may not be ready yet for prime time. The cumulative .NET Framework update was listed as a preview update and as such, should never have been offered as an automatic update on Windows Updates. Microsoft updated the support page of the cumulative .NET Framework update. The company removed the "preview" label from the title and added a known issue to the description. The known issue describes an issue that is no longer in effect. Microsoft confirms that it distributed the KB4481031 update as an automatic update on Windows Update; this happened for a period of 24 hours before the delivery mechanics were changed. For 24 hours, this Jan 22, 2019 Cumulative Update for .NET Framework 3.5 and 4.7.2 (KB4481031) was made available broadly on Windows Update as an automatic update. As of January 23, 2019, this update is no longer offered on Windows Update as an automatic update, but rather only to "seekers" who go to Settings > Update & Security > Windows Update, and then select Check for updates, as is expected. This update continues to be available on WSUS and Microsoft Update Catalog. The update is still available to users who click on the "check for updates" button in the Windows Update interface, and users who access it using WSUS or the Microsoft Update Catalog. No word on whether the updates will get removed from devices automatically but my guess is that won't happen. Administrators may want to check if the KB4481031 update is installed on devices they manage and remove it unless the update fixes an issue experienced on the devices. Closing Words Mistakes happen, but these kind of mistakes should not happen considering that they may push updates that are not ready for wider distribution to a large number of devices. I'm not sure how Microsoft vets updates before they are added to the automatic update distribution queue, but the use of "preview" should have been enough to verify if that preview update should indeed be added to the queue. Now You: How do you handle updates of your devices? (via Woody) Source: Microsoft confirms it distributed KB4481031 in error (gHacks - Martin Brinkmann)
  25. The Startup options on this PC are configured incorrectly – Bitlocker error In this post, we will show you how to fix the error The Startup options on this PC are configured incorrectly for BitLocker. A user may see this error message when he tries to use BitLocker on a Windows system. BitLocker encryption is used to make use of its AES encryption technique to secure the whole volume. It is an alternate to EFS or Encrypting File System. BitLocker is preferred by those who wish to encrypt the whole disk rather than EFS which can encrypt individual files. BitLocker supports the following authentication mechanisms along with an optional escrow recovery key- TPM Only. TPM + PIN. TPM + PIN + USB Key. TPM + USB Key. USB Key. Password Only. This means that a user gets a lot of options for authentication when they use BitLocker. The Startup options on this PC are configured incorrectly You need to make sure that the BitLocker authentication requiring preboot keyboard is enabled in the Group Policy. Type gpedit in the Start search box and hit Enter to open the Group Policy Editor. Now, navigate to the following path inside the Group Policy Editor- Double-click on the configuration listing named as Disallow standard users from changing the PIN or Password to open the configuration page. Finally, set this Policy as Enabled. Now, you need to update this Group Policy. For that, start by opening CMD as Administrator and then execute the following command, gpupdate /force This will update the Group Policies in real time, and you will not be supposed to reboot your computer for the changes to take effect. Source
×
×
  • Create New...