Improved Linux, Sandbox, and Cortana features dominate Build 2004's changelist.
Read the whole story
Read the whole story
All of this works, but it's incredibly messy. It should be much easier to get a WSL2 installation going—ideally, in a single step, whether command-line or graphical. And if there must be multiple steps, they should at least be within the same interface, and all steps referenced cleanly in order in a single set of docs.
As someone who uses WSL, Windows, and standalone-Linux as part of my job, this sentence tickles me as particularly funny. At what point has any power-user feature meant primarily for programmers ever existed in a single step in CLI or graphical on any operating system?
Not saying it shouldn't exist, it'd definitely be great, but as a programmer myself anytime anything is built for programmers, usability is like the last thing programmers think of.
I'm not a programmer and I use WSL. There are PLENTY of good reasons to use it that don't involve writing code.
2004 dropped Cortana reminders and to-do lists without any warning. Previously set a reminder for something important? It's gone! I used to set reminders for things like cancelling website subscriptions, so I was lucky that I realised in time and this change didn't cost me money. Eventually I found that I could access my reminders by downloading the Microsoft To Do app on Android. Most people who used the feature will never discover this as Windows doesn't tell them.
Microsoft has been explicitly telling people this was going to happen, including in the Cortana app for months now. Hell, it even directed me to download To-Do.
Microsoft has been explicitly telling people this was going to happen, including in the Cortana app for months now. Hell, it even directed me to download To-Do.
The Cortana app in Windows 10? I never received any indication that a change was coming.
we're running Windows 10 Build 2004 in a virtual machine under Ubuntu, so our C: drive shows up as "Red Hat VirtIO SCSI Disk Device"
failed again to pay the developer(s) who created Everything search all the $$$ they spent on the salaries of the Windows Search and Cortana teams for the last 20+ years to integrate and deploy a tool that will actually find sh!t on a windows computer, any day, any time, by size, with words inside a file (takes slightly longer than the 0.01 seconds of a normal Everything search), you name it.Microsoft says it noticed how commonly people were turning its Search Indexer service off, so the company
I'd screenshot it for you, but I already did the sync, so now if I open it on a pre-2004 build of Windows, it just says "Synced to Tasks".
I don't think it's a them putting users in front of profits so much as realizing and embracing a strategy that leverages user and developer satisfaction to drive more revenue.First of all, I really like The New Microsoft(tm). First item on the new Windows build is better Linux support? amen.
Second, WSL (I've only used v1) really simplifies cross-platform development flows. Windows is still the king of office work, like it or not, and being able to develop and test locally and offline quickly, and then transfer changes with a simple git pull to the corporate compute farm is very neat.
Thank you Microsoft for putting your users ahead of "maximizing shareholder value." Seems to be working pretty well for everyone.
I don't. After MS noticed people were turning off web searches in cortana in the first versions of Win10, they removed a checkbox and only left a registry key to control that.All the improvements made due to trends Microsoft recognized through telemetry are really cool. Unlike Google's ad tracking and Apple's copy/extinguish motivation, I feel helped instead of harmed.
Do not forget set of new bugs
Storage Spaces eating people's (supposedly resilient redundantly stored) data is not what anyone would call a minor issue either.
I updated to 2004 in release preview stage. Didn't realize that parity storage spaces was broken. A couple weeks later I went to open some files on my parity storage space and they were corrupt. File had same size, same attributes, but data inside was messed up. My onedrive existed on this drive but luckily the corruption didn't sync back. Also, the newly corrupt version of the files didn't get backed up via file history.
I restored the files but on next reboot they started corrupting again. I ran a chkdsk and it made it even worse.
Lesson is, don't update to 2004 if you use parity storage spaces. If you've already updated, roll back, or mark the space as read-only.
Probably because all this talk about bugs is off-topic. This is an article about features.Not sure why you're getting down-voted
Oh come on .. the joke would've been better with floppy disks.One upside of Windows 10 2004: You won't find old install CDs all over the office two decades from now.
No, the [Windows key] + [.] shortcut to bring up an emoji selection panel is news to me. I have never seen it mentioned before, and I do computing support for a living with Windows as the primary OS that I support.
It's been there for a whiiiiiile in Win10. I've relied on it for some time (usually to bring up the emdash shortcut).
I do love Sandbox, but my biggest annoyance is that enabling it breaks VirtualBox. Does it still do that in Win 2004? If not, maybe I'll give it a go again after I upgrade.
Does it break WSL2?
All of this works, but it's incredibly messy. It should be much easier to get a WSL2 installation going—ideally, in a single step, whether command-line or graphical. And if there must be multiple steps, they should at least be within the same interface, and all steps referenced cleanly in order in a single set of docs.
As someone who uses WSL, Windows, and standalone-Linux as part of my job, this sentence tickles me as particularly funny. At what point has any power-user feature meant primarily for programmers ever existed in a single step in CLI or graphical on any operating system?
Not saying it shouldn't exist, it'd definitely be great, but as a programmer myself anytime anything is built for programmers, usability is like the last thing programmers think of.
I'm not a programmer and I use WSL. There are PLENTY of good reasons to use it that don't involve writing code.
I use it for development, but it's also great for remote sysadmin, what with being proper Linux and having a proper ssh client in it.
I also prefer zsh to anything else, and having a full, workable zsh which has access to /mnt/c is incredibly helpful.
failed again to pay the developer(s) who created Everything search all the $$$ they spent on the salaries of the Windows Search and Cortana teams for the last 20+ years to integrate and deploy a tool that will actually find sh!t on a windows computer, any day, any time, by size, with words inside a file (takes slightly longer than the 0.01 seconds of a normal Everything search), you name it.Microsoft says it noticed how commonly people were turning its Search Indexer service off, so the company
All of this works, but it's incredibly messy. It should be much easier to get a WSL2 installation going—ideally, in a single step, whether command-line or graphical. And if there must be multiple steps, they should at least be within the same interface, and all steps referenced cleanly in order in a single set of docs.
As someone who uses WSL, Windows, and standalone-Linux as part of my job, this sentence tickles me as particularly funny. At what point has any power-user feature meant primarily for programmers ever existed in a single step in CLI or graphical on any operating system?
Not saying it shouldn't exist, it'd definitely be great, but as a programmer myself anytime anything is built for programmers, usability is like the last thing programmers think of.
If you don't include at least three command line steps that have to be read from a manual and can't possibly be remembered, you lose the Linux crowd anyway.
RE: Virtual Desktops, believe they have been around since the beginning of Windows 10. The history features (which I don't use personally) I think were introduced in the last couple of years.
RE: Virtual Desktops, believe they have been around since the beginning of Windows 10. The history features (which I don't use personally) I think were introduced in the last couple of years.
RE: WSL Networking, the bridged connection becomes an issue if you're connecting to a corporate VPN developing, which is by and large true for a lot of people because COVID. The NAT based setup, while not perfect, avoids routing issues connecting to resources living on the corporate network like test database servers, source control servers, etc. It's a challenging problem to overcome, but I personally fell like the NAT based setup out the door was likely the best fit for the target audience, developers.
I believe there are real people out there that want, love, and use WSL; I don't understand why. To me it's so much easier to run native Linux and host a windows VM for use when I need it (never).
You're getting buried in downvotes, but let me I say both that I agree with you that it's easier to run Windows as a VM under Linux, AND I understand why people are excited about WSL.
There was a time when I used Windows on the desktop and Linux on the server, pretty much exclusively for both. Being able to have a real, nearly first class citizen Linux right on my laptop--leagues above and beyond Cygwin--would have been an enormous win for me then.
I think there are LOTS of people now in basically the same place I was then; WSL is starting to allow them to blur the lines in interesting ways. It's better than either Cygwin or (from the other direction) WINE, and it's on track to keep getting better.
There's likely going to come a time in the near future where Windows users can run either Windows native apps or Linux native apps just as easily on the same system, all the way down to a laptop, without needing to worry much about the difference. That's pretty awesome IMO.
At home I use Agent Ransack. It's almost instant. At work I have no such privileges, so manually save file paths to create my own index in a OneNote folder in order that I can reliably find every file I need.
I still have no idea why native search in Win10 is so incredibly bad. If there's one thing that a desktop operating system should do, it's help you manage your files.
Can you rearrange the desktops now?Beginning with Build 2004, users can give each of their Virtual Desktops a name of their choosing, whether functional or frivolous. You might name three Virtual Desktops Browsing, Company, and Design—or Elrond, Frodo, and Gandalf. Windows 10 won't judge, and neither will we.
No, the [Windows key] + [.] shortcut to bring up an emoji selection panel is news to me. I have never seen it mentioned before, and I do computing support for a living with Windows as the primary OS that I support.
Blew my mind too. That's why I covered it more thoroughly than just "moar kaomoji."
I also didn't know the term "kaomoji" until discovering that 2004 added "more" of them. NGL, I'm a little jealous; gets old googling the shruggie and copying and pasting it!![]()
Actual advice:
Microsoft should ditch it's current Windows Update approach and the entire SxS methodology. Those directories are a mess ripe for exploitation and NOONE knows what is really in them or how they are being used.
They should instead use an active-passive root partition scheme to allow updating the entire OS as a single unit, instead of package by package. In this way the updates are quick, reliable and able to be easily rolled back. It is silly to distribute individual patches that require an install versus a binary partition drop. Then you know all the OS's are the same in the field.
This is how Chromebooks does it, and provide a high level of consistency across systems.
This requires a rethink of how the C: drive is layed out. True separation between UserData, Config, Libraries and OS files.
Also the registry is due for a revamp, or rather a deprecation. If you turn on sysmon, and see how inefficient your system is in making calls, you would question how there are even cpu cycles left for actual OS use.
I am hoping someone in Microsoft can start to address the real issues in the underlying OS, instead of slapping GUI after GUI on it, when XP was still their best UX.
I just upgraded my natural 4000 keyboard to its successor, and it has a dedicated emoji button! It is where the context menu button belongs! I hate it. It can be reassigned, luckily, but the context menu button itself (which is wrongly moved to the left side of the keyboard) cannot. Boooo!
At home I use Agent Ransack. It's almost instant. At work I have no such privileges, so manually save file paths to create my own index in a OneNote folder in order that I can reliably find every file I need.
I still have no idea why native search in Win10 is so incredibly bad. If there's one thing that a desktop operating system should do, it's help you manage your files.
My approach is
1) File Locator to look for stuff in a given folder. Works well enough that I don't have to RDP into file servers, but may be slow. On boxes where I'm the sole admin & user, register it as the F3 handler.
2) If the basic or regex search in file contents does not cut it, open WSL or Git Bash and grep/ripgrep whatever -- WSL is blocked by corporate policy though :/
Notepad++ Find in files works well too.
3) Everything.exe when I look for a specific item I don't remember where it's saved
To go back on topic, it's good that Docker now has published the WSL2 integration in Docker Desktop Stable 2.3.0.2. It will allow more people who don't own a Pro (Hyper-V) SKU to both access a (WSL2) Linux instance and containers, relatively easily.
It's quite bad for the competition though as it causes issues for type-2 hypervisors. VirtualBox added the HV backend in v6.0, but this is the kind of change that could affect stability and frankly I don't fancy this 'totalitarian' approach.
EDIT:
Forgot to say, WSL eliminates the need for both Cygwin and MSYS2. Big thanks to them for providing what was lacking at the time.
I just upgraded my natural 4000 keyboard to its successor, and it has a dedicated emoji button! It is where the context menu button belongs! I hate it. It can be reassigned, luckily, but the context menu button itself (which is wrongly moved to the left side of the keyboard) cannot. Boooo!
https://www.bleepingcomputer.com/download/keytweak/
That might do what you want. I use it to remap right-ALT on my 101 key Model M to be the Windows key.
I just upgraded my natural 4000 keyboard to its successor, and it has a dedicated emoji button! It is where the context menu button belongs! I hate it. It can be reassigned, luckily, but the context menu button itself (which is wrongly moved to the left side of the keyboard) cannot. Boooo!
https://www.bleepingcomputer.com/download/keytweak/
That might do what you want. I use it to remap right-ALT on my 101 key Model M to be the Windows key.
I use this on lenovo laptops that moved the printscreen key. I should try it. Certain keys are not remappable but context menu is a newer one so it probably can.
I am mostly annoyed they made the buttons smaller and crammed 2 where it was once 1. So I will probably remap it to be a second windows key, which seems idiotic...
My device "is no ready yet" for 2004. I have no idea what the hell I'm supposed to do to make my PC ready. On the bright side; I may be avoiding boatload of troubles from the update.