Why ever did i chose winblows 10

6 minute startup???
Wtf
I'm no windows fan but my windows 10 boxen start in seconds
 
Johnatan56 said:
In regards to update downloads, set your connection to metered, also works for ethernet.

If you don't like Windows, move to a Linux OS, not sure what's stopping you.
Click to expand...

Very little actually is stopping me, if you can tell me which wireless usb modem i can go and purchase that will work out of the box with linux i will install Linux right now, currently i have a WN722N and tried a WN823N v2 wireless adapter on linux and it did not work,.

Linux does see the internet connection, i can connect to my router fine, but somehow it does not know how to communicate/work with the device as it does not connect to the internet at all.

I have in detail produced my problem and all the errors i got and have gotten many solutions by the helpful linux guys on another forum but still did not solve my problem.

Which modem will work by just installing the drivers.
 
Last edited:
No fooling, 6minutes indeed. You come to my house and i show you in realtime..
 
FlyUAv said:
Very little actually is stopping me, if you can tell me what wireless usb modem i can go and purchase that will work out of the box with linux i will install Linux right now, currently i have a WN722N and tried a WN823N v2 wireless adapter on linux and it did not work, Linux does see the internet connection, i can connect to my router fine, but somehow id does not know how to communicate/work with the device as it does not connect to the internet at all. I have in detail produced my problem and all the errors i got and have gotten many solutions by the helpfull linux guys on another forum but still did not solve my problem.
Click to expand...

https://www.howtogeek.com/howto/43752/how-to-install-a-wireless-card-in-linux-using-windows-drivers/

You could try it yourself.
 
I have heard this same rant starting around windows 95...

Things move on.
 
FlyUAv said:
No fooling, 6minutes indeed. You come to my house and i show you in realtime..
Click to expand...

Even with a hard drive instead of an SSD (and if that's the case, come on man it's upgrade time), Windows shouldn't be so slow. It's possible you need a fresh format after upgrading to Windows 10. When I first upgraded the system had weird glitches, so I did a proper reformat and never had an issue again.

Both on my current 1TB Samsung 850 EVO SSD & previous 128GB SSD, Windows 10 takes around 10 seconds to boot up.
 
Alright, I'm bored.

FlyUAv said:
I am going to give the very short story, get this, you cannot simply do a peer to peer connection nor can you simply do a lan connection, and YES i went through countless of pages of research and used many troubleshooting methods myself to NO avail. So many people having endless problems it makes one sick just to read half of it
Click to expand...

I can do that just fine. I can do it on the APIPA range or through static IPs.

FlyUAv said:
When i finally got the dumb homegroup option to work, only to find that it goes into a never ending connection spree once entering the stupid password, Never actually connecting the pc's
Click to expand...

Homegroups are officially deprecated in Windows 10 1709. The options are still there, but they will probably be removed in a cumulative update to 1804.

FlyUAv said:
When i do that it displays a continious message "identifying" on both pc's its all it does for eternity.

I got so far as to manually configure the ip adresses on both pc's, (not that it was needed because both network cards did display that it obtained valid ip adresses, and on both pc's windows identifies the network cards respectively 100% and they are working perfectly as i made connections before on earlier operating systems sucessfuly between 2 pc's, both is set to WORKGROUP and am on the same subnet. but on win 10 i only get "identifying" when the cable is plugged into both pc's
Click to expand...

If you're stuck on "identifying" that tells me one of your machines is looking for a DHCP server still, or is having an issue with defaulting to the APIPA range. Maybe resetting your network adapters would help. That's an option in Settings > Network and Internet > Network reset (scroll down to find it).

FlyUAv said:
The network cards is the built in type into motherboard, the one pc is an asus motherboard from 2011, and the other pc is a asrock mortherboard from 2016.

...

I then plugged one pc into the wireless router, and the pc's was able to see each other but could not connect to each other.

I did come right with an adhoc connection, can someone tell me if there is a way to boost the power to a thumbdrive wireless usb adapter so i can stick it onto a usb extension cable of 5 meters, so that i can position the wireles adapter in such a way to get a more direct straight line to the other pc, that should work but the small usb wireless adapter does not respond on a usb cable extension, and the WL722 usb adapters that does work on an extended cable is nowhere to be sold in my town.
Click to expand...

I'm going to guess that the PC having most of the issues is the one with the motherboard from 2011. If you could see the other PC on Network Neighbourhood but not connect to it, that's a DNS issue. Resetting the network adapter settings should fix it.

I had this issue on Windows XP years ago, but I could navigate to both computers using their IPs in WIN+R.

FlyUAv said:
O please how old are you 12 ? Not for you to judge what my skills are, i did my MCSE back in the day, and worked in the industry for 6 years, i worked for 3 big IT companies and YES i can give you the references to contact to find out for YOURSELF how well i provided my services, anytime pal just ask me ;) not that i need to prove anything to YOU whoever YOU are, but i will GLADLY give you the contact numbers.

Understand that there are many IT people that cannot solve every single problem, let me tell you it is impossible, even for YOU, so don't come here and try and be a clown..in getting something to work sometimes the solution is something no one thought about, Look at my problem for instance, Not a single working solution from anyone yet as to what EXACTLY my problem is....So almighty IT GRANDMASTER if YOU are so good, What is YOUR solution ??????? But If you are here to troll about rather let someone with a solution reply as i am not interested in your meaningless discussion.
Click to expand...

Reminds me of: http://knowyourmeme.com/memes/navy-seal-copypasta

FlyUAv said:
  1. Devastating Windows rot (might be solved in future Windows releases if developers switch from Win32 to UWP).
  2. No enforced file system and registry hierarchy (I have yet to find a single serious application which can uninstall itself cleanly and fully). The $USER directory in Windows, specially in Windows 10, is an inexplicable mess.
  3. svchost.exe (the whole philosophy of preserving RAM this way became outdated years ago).
  4. No true safe mode (rogue applications may easily run in it).
  5. No clean state (for most OEM installations out there). This will be finally solved in new Windows 10 builds.
  6. The user as a system administrator (thus viruses/​malware - most users don't and won't understand UAC warnings).
  7. No good packaging mechanism (MSI is way too fragile).
  8. No system-wide update mechanism (which includes third party software - to be fair there are third party applications which offer this functionality, but then such applications don't support core Windows updates).
  9. In certain cases it's extremely difficult to find or update drivers for your hardware devices (anyone who's tried to install a fresh Windows onto their laptop will testify).
Click to expand...

  1. That's the NTFS legacy, file rot. Won't be solved for a long time, but SSDs mask over the issue quite well. I also haven't had to deal with file rot issues since the launch of Windows 8.
  2. This is why Microsoft is moving to UWP and a flatpak/snap-like method of managing files and dependencies. This issue will be gone by 2020.
  3. Legacy stuff - gone by 2020.
  4. Meh. How big of an issue is this today, really?
  5. The "Reset this PC" option takes most of the pain of dealing with bloatware out of the equation.
  6. Legacy stuff - gone by 2020.
  7. Legacy stuff - The .appx file format is a good replacement, even for Win32 applications.
  8. Legacy stuff - This is changing.
  9. I haven't run into this issue for years. My Windows 10 ISOs have always included network drivers for most platforms, with some exceptions for platforms that only have 32-bit drivers available or are very unpopular.

FlyUAv said:
  1. Windows is extremely difficult to debug (e.g. try finding out why your system is slow to boot).
  2. Windows boot problems are too often fatal and unsolvable unless you reinstall from scratch.
  3. Windows is hardware dependent (especially when running from UEFI).
  4. Windows updates are terribly unreliable, very slow (to install) and they also waste disk space. The only released Windows 7 SP1 cumulative update, totally breaks the Windows Updates service (the worst piece of software in human history).
  5. Windows cannot replace system DLLs on the fly and restart corresponding services which depend on said DLLs due to its architecture. As a result some system updates require multiple reboots (innocuous malevolence in me requires to mention that in Linux you can even update the kernel on the fly).
  6. Windows keeps trying to reinstall failed updates over and over (in certain cases every such cycle of "updating" can render your PC disabled for hours!).
  7. There's no way to cleanly upgrade your system (there will be thousands of leftovers), etc.
  8. The Windows OS installer doesn't give a damn about other OSes installed on your PC and it always overwrites the MBR. In case of already existing Windows installations, it sets the newly installed Windows as the default OS - no questions asked. In case of UEFI, booting of other non-Windows OSes is unsupported and Windows actively prevents this.
Click to expand...

Let's continue:

  1. CTRL+ALT+DEL > Task Manager > Start-up. That gives you hints of where to start. If you want more verbose feedback, you can do this in the Windows Assessment Toolkit: https://docs.microsoft.com/en-us/wi...ing-performance-and-responsiveness-exercise-1
  2. Meh, I don't think this is true. Some issues can cause file corruption, but they're rare.
  3. Not sure what to make of this one.
  4. We know, it's been an issue for years since the launch of XP. It got fixed in Windows 8. Windows 7 needs a lot of babying to get it updated correctly, but most of that is down to how Windows Update used to check for applicable updates according to a manifest that it had to read serially.
  5. This isn't really an issue for systems which are not mission-critical. They're working on this in any case, though kernel updates will always require a reboot.
  6. That's why update releases are staggered so that only a small number of people see this problem while Microsoft holds those updates back to fix them. Rolling release isn't easy.
  7. Legacy stuff - gone by 2020.
  8. This is both a UEFI platform issue and a Windows issue. Still, I can easily edit GRUB to get back to where things were before the update, and I can UEFI boot both Windows 10 and Ubuntu 1709 on my system.
 
FlyUAv said:
  1. WinSxS, though a neat idea, turned into some madness: Windows keeps the versions of files the user won't ever need: for instance the English version of Windows will have copies of files for many other languages irrespectively of the chosen locale or MUI.
  2. Most malware writers target Windows as the most popular desktop OS, so it has the biggest number of viruses among all other OSes (over five thousand new viruses daily).
  3. Windows loves thrashing your HDD.
  4. Microsoft programmers are still unable to cope with NTFS fragmentation twenty-five years after its introduction. To make things worse most Windows applications do not preallocate files thus they contribute to fragmentation even more.
  5. Windows anti-virus products oftentimes make your PC less safe - so if you want perfect security and privacy, stop using Windows and migrate to Linux right away. OEM updaters make your PC wide open for attacks.
  6. Microsoft has recently decided that you will no longer be able to download certain Windows updates manually. You'll only be able to get them via Windows Update.
  7. "sfc /scannow" is offered as a solution to most Windows Update Service and Microsoft Installer Service errors, yet in 95% of cases it's totally ineffective.
  8. Windows does not allow you to use any partitions other than the first one on your removable USB flash drive. There's no logic or explanation behind this totally ridiculous and artificial limitation.
  9. Windows does not automatically clean temporary files ever, however it must do that for every reboot/power cycle.
  10. The generic drivers Windows comes with are not always compatible with the wide range of existing hardware. Since Windows has a habit of replacing your vendor's drivers with its own newer drivers your hardware may stop working correctly after upgrading to a newer Windows release
  11. Microsoft has gone crazy: Windows 10 is now a recommended update for all Windows 7/8.1 users unless you're running their Enterprise versions. That means your computer will automatically update to Windows 10 unless you either disable the Windows Update service completely or set Windows updates to the manual mode.
  12. In May 2016 Microsoft started deceptively updating users' PCs to Windows 10 regardless of your Automatic Windows Updates settings or the way you interact with the GWX application.
Click to expand...

  1. This is a holdover from Windows 7/8. There's an alternative already available, but it requires an easy way to set it up for consumers and OEMs, and OEMs in particular need to start using it on all their systems. Windows 10 Lean is probably the key do getting this done.
  2. This isn't really a problem of Microsoft's making. Linux servers are under an equally large threat daily.
  3. Only if you've set it up with all the defaults and don't realise what's causing it. And most of the time it's older hardware and drivers. I've seen this on other systems, but never my own.
  4. Legacy stuff - gone by 2020 with the arrival of ReFS.
  5. Only if you're using something that does weird things like performing MITM file inspections on your system. I'd say that using third-party AV systems today instead of Defender, which has a much more robust set-up and is a lot more aggressive, makes no sense.
  6. The needs of the many outweigh the needs of the few. It's not ideal, but it works. If you want that kind of control, use NT Offline Updater Tool.
  7. Legacy stuff - gone by 2020. See 1.
  8. Meh. Why do you need them?
  9. Meh. Why do you need this? You can schedule it yourself.
  10. This problem is going away as of 1804, IIRC. Drivers should have been re-architected long ago after the changes made in Windows 8.1.
  11. I agree with them for the most part. It makes more sense to be on Windows 10 than 7 or 8 these days, except if you have special requirements. Besides, how else are they going to make money off the Store?
  12. I haven't seen this happen at all recently after the update lawsuits.
 
FlyUAv said:
In April 2017 Microsoft published a list of things it's collecting from your PC at the basic telemetry setting (Web Archive copy).
Wow, just wow: Microsoft now openly publishes its collected data in regard to Windows 10 users:
"Over 44.5 billion minutes spent in Microsoft Edge across Windows 10 devices in just the last month" - we spy on Edge users.
"Over 82 billion photos viewed within the Windows 10 Photo app" - you're using our Gallery app, right? Great!
"Gaming continues to grow on Windows 10 – in 2015, gamers spent over 4 billion hours playing PC games on Windows 10" - we now know what apps you're running and for how long.
Click to expand...

I just wanted to highlight that the bolded part is literally what they're reporting, and you can do this as a system admin on users inside your own network, so...

Microsoft has been collecting telemetry for years, it's what drives their systems and helps them figure out what needs fixing.

FlyUAv said:
Starting October 2016 telemetry (spying) became impossible to disable in Windows 7 and 8.1 because Microsoft changed the way it distributes updates for those two operating systems.
Windows 10 Enterprise, which is the only version where ostensibly telemetery can be fully disabled, is still contacting various data collection servers despite your privacy settings.
Microsoft's EULA grants Microsoft the rights to use any of your content related to the services like Bing, Cortana (a built-in file indexer and search in Windows 10), OneDrive or Skype: "you grant to Microsoft a worldwide and royalty-free intellectual property license to use Your Content". You can read Microsoft's response here which paints everything in a positive light however after Snowden's leaks it's hard if not impossible to take them seriously.
Click to expand...

1) I believe in the latest version of Windows Internals that it's stated that the telemetry collection in Windows 10 Enterprise is merely to tell Microsoft how many people are refusing the collection of telemetry data. They need to keep track of that for legal purposes especially in the EU.
2) This isn't specifically a right to use copyright content, to be fair. This gives Microsoft the ability to move your data across data centers and country borders. "Use" in legal terms means something very different, especially when it comes to search and indexing because they need to know how accurate their services are.

FlyUAv said:
Microsoft pushes Windows 10 so hard it actually started spreading FUD even about its own older OSes:
Microsoft started lying through their teeth about Windows 7: "We do worry when people are running an operating system that's 10 years old that the next printer they buy isn't going to work well, or they buy a new game, they buy Fallout 4, a very popular game, and it doesn't work on a bunch of older machines. And so, as we are pushing our software vendors and hardware partners to build great new stuff that takes advantage of Windows 10 that obviously makes the old stuff really bad and not to mention viruses and security problems".
Egregious lying continues: Microsoft falsely states that newer Intel and AMD CPUs will only be supported by Windows 10. If that were actually true you wouldn't be able to run MS-DOS on Intel Skylake yet you can, perfectly (edit: later, Microsoft reneged on not supporting Skylake CPUs). Perhaps they are talking about new advanced features of the said CPUs, but their wording means the opposite: like you cannot physically run any older Windows releases on these new CPUs.
Microsoft is getting desperate: the users of Intel Kaby Lake CPUs and AMD Ryzen CPUs will no longer receive Windows 7/8.1 updates at all. More information.
Click to expand...

Coming from someone who's apparently written their MCSE "back in the day" I expected that you could see through this for what it is. Drivers for printers are currently architected differently because they cannot run in kernel mode on Windows 10. Fallout 4 is a bad choice, but games which require DirectX 12 definitely qualify, and there will be some machines where NVIDIA or AMD abandoned legacy drivers so they can't be launched properly. Both EFI and chipset software is also changing, and that's something you would always have to backport and clumsily change to suit Windows 7 and earlier OSes.

Like Advanced Format drives, which became popular during the Windows 8 years. Those required different drivers for Windows 7 because it didn't have any way to interface with their more advanced controller features, and 4K Native AF drives still don't work on Windows 7. They'll format into 512k sectors and run with reduced performance when writing to the drive. 10% performance loss on a HDD isn't that much compared to a 10% drop in performance on an NVMe drive.

Things like the Meltdown and Spectre patches on Skylake machines running Windows 7 will also be problematic. That's a configuration that was not supported by Microsoft or Intel, it won't be using a tick-less kernel, and the patches for those machines won't be tested properly.

FlyUAv said:
Microsoft has lost its mind and they now aggressively try to foist/force Windows 10 on unsuspecting users. Oh, it's now official: they will forcefully install it everywhere they can in 2016.
Click to expand...

Again, I haven't seen this behaviour since they got sued for this in the US. The aggressive nature of the installer isn't a problem anymore. It was a problem, and it was a ****ty decision, but that's how they got on the road to 500m users.

FlyUAv said:
  1. Windows 10 will forever be beta software (specially after they fired a large chunk of their QA/QC department and instead delegated testing to the insiders):
  2. A new model of development with no Windows 11 in sight.
  3. Two Control Panels (read below).
Click to expand...

  1. Could say this about any rolling release, really. If anything, Microsoft is finally matching Fedora and Ubuntu release timelines, which miraculously have pulled themselves together just as well.
  2. I think we both know that the name is just marketing.
  3. I'm sure you've noticed the scaling back in the reliance on old systems and menus in favour of the new Settings menu in Windows 10. 1804 makes a lot of changes in this regard.
 
FlyUAv said:
  1. You've got no real control over crucial features of the OS:
  2. Windows 10 will have no service packs which means it will always be a work in progress and you are a perpetual beta tester.
  3. Forced updates you cannot opt out of (and Microsoft have borked quite a lot of them recently so prepare to see your Windows die after installing a new batch of updates - actually Microsoft has already borked one update, read horror stories about KB3081424). In December 2016 Chris Capossela, chief marketing officer at Microsoft, admitted that the company had gone too far with the way Windows updates are distributed.
  4. Safe Mode has become impossible to access unless you've booted into ... the running OS, which totally defeats its purpose. Also Safe Mode is hidden behind almost a dozen of steps vs. a single F8 key press on boot in every Windows version from 95 to 7.
  5. Windows 10 anniversary update makes it very difficult (read impossible for average users) to disable Cortana.
  6. Windows 10 violates basic networking principles: it ignores the hosts files, the DNS protocol and firewall rules and sends telemetry data regardless
.
Click to expand...
  1. Hey, it's closed-source software, waddya know!
  2. Rolling release.
  3. Rolling release, and they've had very few disaster updates since 2016 after they changed how they tested things. You should stop holding grudges, they're bad for your health.
  4. Microsoft changed their corporate ethos under Nadella, so of course they'll do things in a ham-fisted way and attempt to fine-tune them later. That's how they roll.
  5. Safe mode is accessible if the OS detects that it is having problems rebooting and sends you to the repair menu. At which point, it is fairly trivial to tell it to boot into Safe Mode.
  6. Cortana is being baked into Windows 10 as an AI interface. Get used to it.
  7. It does? How does it-wait, I'm not going to ask. We don't want another page-long summary of how Windows apparently ignores its own firewall rules for telemetry collection.
FlyUAv said:
Microsoft says that there will be at least two service updates (or whatever their names are) for Windows every year, and each update is basically a new version of Windows, so:
  1. Twice per year you may reinstall software deemed not required by Microsoft.
  2. Some features you grew dependent on will be removed without providing any alternatives.
  3. Your preferences will be reset to default, so you'll need to go through them regularly.
  4. Some Metro applications will be reinstalled if you deleted them previously. New wonderful Metro applications will be installed.
  5. Expect your group policy settings and tweaks to be completely removed or changed and the only way to get them back is to upgrade to Windows 10 Enterprise.
  6. Certain software titles and drivers will cease to work.
  7. Two kinds of font antialiasing (ClearType v2 for classic applications and some awful dirty grayish something for Modern apps).
  8. All kinds of varying visual decorations and styles (some people have discovered up to seven varying styles in Windows 10).
  9. Absolutely dissimilar classic and modern (PC settings) control panels.
  10. Different font faces and sizes all around.
  11. Different styles of settings for modern apps.
  12. Absolutely different context menus and their appearance in different applications and apps.
  13. Terrible hardly-configurable appearance, dubious design choices and extremely limited functionality (vs Windows 7/XP):
  14. Two Control Panels with absolutely zero thought given to how they differ and why each one should be used.
  15. Some Control Widgets are spread between the two Control Panels which is utterly confusing (e.g. User Management).
  16. No Windows classic UI for windows decorations. Windows decorations can hardly be configured at all in Windows 10.
  17. An awful choice of colors/palette
Click to expand...
  1. It's like this on Fedora and Ubuntu if you upgrade with each version, and Apple does a MacOS update yearly (and Apple will push through software in an absolutely broken state in order to meet deadlines and move to fixing their release or updating it)
  2. Hey, it's closed-source software, waddya know! Don't get too comfortable with it.
  3. This was fixed in Windows 10 1703, so anyone who updated to 1709 should have seen their settings maintained. If not, this will get fixed over time. It's a rolling release!
  4. See 2 and 3.
  5. A lot of group policy stuff is old and deprecated and plain doesn't work in Windows 10. MDM and AAD is the way forward here.
  6. See 2.
  7. They're still replacing those systems. It's a lot of bloat they have to deal with.
  8. Microsoft has never had someone in charge of UI for Windows 10 before (that is now Joe Belfiore's domain), so this will change. Also, their philosophy is ship-new, not fix-shipping.
  9. See 8.
  10. See 8.
  11. See 8.
  12. See 8.
  13. See 8.
  14. See 8.
  15. See 8.
  16. See 8.
  17. See 8.
FlyUAv said:
  1. Absolutely awful, childish and amateurish icons (the current release features slightly better icons) as if we live in the era of eight-bit displays (only rivalled by those in Windows 3.1 from 1992). Windows 2000 in 1999 looked better than Windows 10 in 2015.
  2. A big number of Windows 10 apps are still NOT on par with their classical counterparts from Windows 7/Vista/XP (many features are missing or many options are not configurable).
  3. It features huge mandatory system and apps updates (you cannot disable them, you can only postpone the system reboot after their installation).
  4. As if it wasn't enough, Windows 10 gets downloaded automatically if you run Windows 7 or 8.1. We are talking about 3-6 gigabytes of data some people absolutely do not need.
  5. It uses your free bandwidth to distribute updates to other users nearby you.
  6. Windows 10 Pro edition has become more or less unsuitable for small enterprises because Windows 10 anniversary update removes the ability to disable the following "features" (more like annoyances)
Click to expand...
  1. Dude, you should stop using your 16-bit display on Windows 2000. It does support a 32-bit colour space.
  2. Ship-new, not fix-shipping. Also, hey, it's closed-source software, waddya know! Don't get too comfortable with it.
  3. I can stop Windows Update from applying major updates to my father's PC while he's out at sea on a mobile connection, using the settings in Settings and disabling the Update orchestrator and Windows Update services.
  4. Well, it is a recommended update, so... also, see 2.
  5. You can turn this off.
  6. Microsoft wants enterprises to use the Store options they have available to them to simply and automate app deployment and setting up new computers and using MDM to better control which applications get delivered to which user. All of those features have special options for enterprise users.
 
FlyUAv said:
Visual Studio 2015 C++ compiler secretly inserts telemetry code into binaries.
Click to expand...

See: https://www.reddit.com/r/cpp/comments/4ibauu/visual_studio_adding_telemetry_function_calls_to/

Steve Carrol said:
hi everyone. This is Steve Carroll, the dev manager for the Visual C++ team.

Tl;dr: thanks folks for the feedback. Our team will be removing this from our static libs in Update 3.

Our intent was benign – our desire was to build a framework that will help investigate performance problems and improve the quality of our optimizer should we get any reports of slowdowns or endemic perf problems in the field.

We apologize for raising the suspicion levels even further by not including the CRT source, this was just an oversight on our part. Despite that, some of you already investigated how this mechanism works in nice detail. As you have already called out, what the code does is trigger an ETW event which, when it’s turned on, will emit timestamps and module loads events. The event data can only be interpreted if a customer gives us symbol information (i.e. PDBs) so this data is only applicable to customers that are actively seeking help from us and are willing to share these PDBs as part of their investigation. We haven’t actually gone through this full exercise with any customers to date though, and we are so far relying on our established approaches to investigate and address potential problems instead.

We plan to remove these events in Update 3. In the meantime, to remove this dependency in Update 2, you should add notelemetry.obj to your linker command line. If you’re generally concerned about phone-home scenarios, more information about how to configuring Windows 10 appropriately to your needs can be found here: https://technet.microsoft.com/en-us...top-data-flow-to-microsoft#bkmk-priv-feedback

Thanks.
Click to expand...

FlyUAv said:
  1. Windows 10 anniversary update blocks all drivers which are not signed by Microsoft. At the moment the ext2fsd driver and VirtualBox will cease to function.
  2. In Windows 10 certain not-so-old games and applications either do not work or have severe problems.
  3. Windows 10 shows full-screen ads on your lock screen.
  4. March 2017 update: Windows Explorer now shows ads for OneDrive.
  5. A new shocker: Windows 10 installs apps behind your back without your approval. The first Windows anniversary update without asking first reinstalls Skype and auto-logins you.
  6. As has already been mentioned, different Windows 10 releases are different operating systems altogether, so Microsoft is "free" to deprecate the support for your hardware even if it came with Windows 10 preinstalled. So, Microsoft decided it no longer wants to allow new Windows releases on PCs having an Intel Clover Trail Atom CPU inside.
Click to expand...
  1. As it should be. Unsigned drivers are a security risk that Microsoft was requested to plug, and so they did. I believe that the VirtualBox drivers are now signed and the ext2fsd developers re-signed with the correct key.
  2. I experience this with Borderlands 1 & 2. Windows 10 is definitely an issue, but I fixed it by upgrading to AMD Ryzen from the Core 2 and Phenom chips I was testing with. Microsoft shares part of the blame, but it's also down to Gearbox and 2K not willing to patch or offer support for these titles.
  3. I've literally never seen this, and I use the Bing wallpapers for the lock screen.
  4. Hey, it's closed-source software, waddya know! Don't get too comfortable with it.
  5. See above.
  6. When Windows 10 was introduced, Microsoft said that systems using it would receive updates for the lifetime of the device. That's around ten years, but only if you stay within the supported window for Windows 10 operating system versions. Clover Trail was both Microsoft's and Intel's fault, but it was more Intel's fault that they just couldn't get the driver development done. So you should really yell at Intel, not Microsoft.
 
o man you barn stormed this one, though i can counter many of the replies, i just don't have it in me right now, had a bad week. so many things in winblows can be done differently and much more efficiently... anyway cheers for your thoroughness and eagerness to reply on every point, have a good one.
 
Last edited:
FlyUAv said:
o man you barn stormed this one, though i can counter many of the replies, i just don't have it in me right now, had a bad week. so many things in winblows can be done differently and much more efficiently... anyway cheers for your thoroughness and eagerness to reply on every point, have a good one.
Click to expand...

Yeah... CataclysmZA actually put some thought into the post, and tried not to randomly fire blanks like you do... hence the lack of a cognitive response from you.

Hey, but you're the tech expert.

As you say - have a good one. ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X