Windows 10 Insider Preview Dev Build 20246.1 (fe_release) - Oct. 29 Insider

Page 9 of 10 FirstFirst ... 78910 LastLast
  1. martyfelker's Avatar
    Posts : 2,430
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #80

    fifothekid said:
    I do not want to disable Hyper-V. VMWare 16 does support Hyper-V and I've been using them together for sometime now. Only in the last two updates it stopped working.
    I am using VMware WS 15.5.6 because VMware removed the VMware Server (i.e. Shared VMs) from VMware WS 16 (got my money back). It works perfectly fine with Hyper-V - no problems with any build including this one. Just created an Ubuntu 20.10 VM with no problems and have been running a Shared Windows for Workstations without any problems for months. I have two Hyper-V VMs running concurrently.
      My Computers

  2. smactilactus's Avatar
    Posts : 606
    latest Win10 Insider build
       #81

    fifothekid said:
    So I'm having two problems with this update:
    1- There is no way to permanently disable Windows Defender! Tried with gpedit, tried disabling tamper protection, tried with registry, and nothing seems to work! In the comments here you can find more detailed discussion about how it can be done:
    Can't disable Windows Defender via Group Policy or the Registry - Super User
    2- Starting from the previous version, both my VirtualBox and VMWare Pro/Player stopped working! They give weird errors with no indication to the problem. Tried with new and old virtual machines still the exact same error. Copied them to another machine and they worked!
    Now I'm trying with Hyper-V manager..
    Why are you trying to disable Defender. It works perfectly well. It's the ONLY security software I've used for years, and my system has ZERO problems. Just curious...
      My Computer


  3. Posts : 15
    Windows 10
       #82

    smactilactus said:
    Why are you trying to disable Defender. It works perfectly well. It's the ONLY security software I've used for years, and my system has ZERO problems. Just curious...
    It does work perfectly, agree. The thing is, I don't want anything to slow down my programming experience.

    - - - Updated - - -

    martyfelker said:
    I am using VMware WS 15.5.6 because VMware removed the VMware Server (i.e. Shared VMs) from VMware WS 16 (got my money back). It works perfectly fine with Hyper-V - no problems with any build including this one. Just created an Ubuntu 20.10 VM with no problems and have been running a Shared Windows for Workstations without any problems for months. I have two Hyper-V VMs running concurrently.
    Oh really? I thought that support started from VMWare Workstation 16. Silly me!
      My Computer

  4. Brink's Avatar
    Posts : 56,224
    64-bit Windows 10 Pro for Workstations build 21354
    Thread Starter
       #83
      My Computers

  5. martyfelker's Avatar
    Posts : 2,430
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #84

    fifothekid said:
    It does work perfectly, agree. The thing is, I don't want anything to slow down my programming experience.




    - - - Updated - - -

    tarted from VMWare Workstation 16. Silly me!
    Not at all. VMware did not advertize this very well - maybe not at all. But M$ noticed and because VMware is now ownded by Dell were (I believe) able to force VMware to ditch VMware Server.
      My Computers


  6. Posts : 1
    10
       #85

    bncz135 said:
    This definitely started on build 20241 for me. Scanning feedback for "torn write" shows several other users with the same problem including those who ended up with a non bootable system.
    I am getting it as well. Drive d in my laptop, I copied everything deleted the partition, recreated it and copied everything back and this messaged stopped, obviously it will be more problematic for drive c.

    A little scary. Does a torn write imply data loss?
      My Computer

  7. thewizardoz's Avatar
    Posts : 124
    Windows 10 Pro x64 Insider Preview Build 18875.1000 20H1
       #86

    Does anyone have any followups on this write error problem please?


    Does anyone have any followups on this write error problem please?

    Thanks.
      My Computer

  8. jimbo45's Avatar
    Posts : 10,463
    Windows / Linux : Arch Linux
       #87

    martyfelker said:
    Not at all. VMware did not advertize this very well - maybe not at all. But M$ noticed and because VMware is now ownded by Dell were (I believe) able to force VMware to ditch VMware Server.
    Hi there
    That's one of the reasons I wanted to be absolutely independent of VMWare - Dell was nenver one of my favourite companies in the first place.- I've managed finally (was quite a lot of work) to get legacy studio hardware etc working on an XP VM on KVM.

    It was harder than getting W10 etc working properly as a VM -- remember XP no SATA devices etc so had to use a bit of trickery to get everything to work really fast. Current versions of Windows 10 work OK as VM's -- I have to query though why a whole load of people are using the latest builds essentially as "Production Machines" and then get vexed when they don't always work as expected. Keep your "Everyday machine" reasonably standard and mess around with the new stuff as VM's - if things break no problem to ditch that VM and create a new one without all the hassle of hosing up a machine you use daily for regular work.

    VMWare server was quite useful in its day. Currently if you logoff on Windows and you have a number of VM's running then it's a real pain with vmware !!!!!

    Cheers
    jimbo
      My Computer

  9. martyfelker's Avatar
    Posts : 2,430
    Windows Insider Fast Ring LatestKUuuntu 20.10
       #88

    jimbo45 said:
    Hi there
    That's one of the reasons I wanted to be absolutely independent of VMWare - Dell was nenver one of my favourite companies in the first place.- I've managed finally (was quite a lot of work) to get legacy studio hardware etc working on an XP VM on KVM.

    It was harder than getting W10 etc working properly as a VM -- remember XP no SATA devices etc so had to use a bit of trickery to get everything to work really fast. Current versions of Windows 10 work OK as VM's -- I have to query though why a whole load of people are using the latest builds essentially as "Production Machines" and then get vexed when they don't always work as expected. Keep your "Everyday machine" reasonably standard and mess around with the new stuff as VM's - if things break no problem to ditch that VM and create a new one without all the hassle of hosing up a machine you use daily for regular work.

    VMWare server was quite useful in its day. Currently if you logoff on Windows and you have a number of VM's running then it's a real pain with vmware !!!!!

    Cheers
    jimbo
    VMware was bound to bought up again by a larger company - I'm not excited by Dell Technologies but if it would have bought by say Microsoft it might have just disappeared. I was using VMware from version 1 - they had a very active and engaging bbs type forum. They actually supported OS/2 for a short time but of course IBM would not stand for it. This is why I think Microsoft would have killed it if they bought it. I suspect they were the ones that killed Workstation Server in a deal to let VMware work with Hyper-V = actually a technical feat of virtulization. So it is worthwhile to me to have licenses for both versions 15 and 16. And with 16 on Linux VMware seems to have completely solved upgrading to the latest kernels - you won't see many complaints about that anymore. No doubt QEMU/KVM virt-manager is very nice but I just like the polish of VMware. In fact virtualization on Fedora Rawhide is a pleasure - I may statrt fiddling around with Virtualbox testbuilds again to see what those folks are working. I also have aspirations of working agains after decades with Mathematica, which I've invested in - install find on Rawhide. And Linux just released kernel 5.12rc5 so perhaps I'll play with compiling kernels. I may fool again with WSL - WSL 2 broke the X server I was using.

    cheers,

    mf
      My Computers

  10. jimbo45's Avatar
    Posts : 10,463
    Windows / Linux : Arch Linux
       #89

    martyfelker said:
    VMware was bound to bought up again by a larger company - I'm not excited by Dell Technologies but if it would have bought by say Microsoft it might have just disappeared. I was using VMware from version 1 - they had a very active and engaging bbs type forum. They actually supported OS/2 for a short time but of course IBM would not stand for it. This is why I think Microsoft would have killed it if they bought it. I suspect they were the ones that killed Workstation Server in a deal to let VMware work with Hyper-V = actually a technical feat of virtulization. So it is worthwhile to me to have licenses for both versions 15 and 16. And with 16 on Linux VMware seems to have completely solved upgrading to the latest kernels - you won't see many complaints about that anymore. No doubt QEMU/KVM virt-manager is very nice but I just like the polish of VMware. In fact virtualization on Fedora Rawhide is a pleasure - I may statrt fiddling around with Virtualbox testbuilds again to see what those folks are working. I also have aspirations of working agains after decades with Mathematica, which I've invested in - install find on Rawhide. And Linux just released kernel 5.12rc5 so perhaps I'll play with compiling kernels. I may fool again with WSL - WSL 2 broke the X server I was using.

    cheers,

    mf
    Hi there
    Remember now IBM owns Redhat and hence Fedora !!! I actually don't have too many issues with IBM though apart from CITRIX which regularly broke at least 2 times a week at the last workplace I was at that was using it for virtualising Windows desktops for their clients -- KVM infinitely better these days and it's being used more by cloud servers and enterprise desktop virtualisation.

    I liked their mainframe OS'es back a long time ago (can still run MVS/SP and TSO using Hercules emaulator on a laptop - works both in Windows and Linux) - crazy thing is it's a lot faster than when it was running native on a big 3033 Mainframe years ago !!!!!!.

    Cheers
    jimbo
      My Computer


 
Page 9 of 10 FirstFirst ... 78910 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:35.
Find Us




Windows 10 Forums