Micky wrote:

And I made them bat files and I tried them and.....

wu-disable went by so fast I couldn't read all of it.

They are batch files. They run in a console windows (aka command
shell). Unless you first open a console windows (cmd.exe) to run them
there, the console window will close as soon as the batch file
completes. You don't know how to run console (DOS mode) commands?

Besides, there is really not much to show. It may show whether the
command succeeded or failed but you can see that by looking in
services.msc (or make sure to refresh its display if you have it open at
the time you change service state).

Instead of ending in exit, I thought there was a command that would
end a bat file without closing the cmd box. I thought it was Return,
but that didn't work.

That would require opening the console window (cmd.exe), telling it to
run the batch file but not close the console window afterward.
Basically you are independently opening the console window so what you
run inside doesn't close that window. DOS-mode commands may open a
console window but may not. If you rely on the console command to show
a window, it will get unloaded as soon as it is no longer needed, like
when the console command finishes.

You could:
- Run cmd.exe to load a console window. That console window is owned by
the cmd.exe process, not by any programs started within that console.
- Run wu-enable.bat or wu-disable.bat.
- Since the console window remains open - until you exit cmd.exe - you
can see any stdout produced by any non-GUI (DOS-mode) programs you run
inside that console.
- To exit the console (close the window) means you have to enter the
'exit' command (tells cmd.exe to unload) or you use the titlebar icons
or control menu to close the window (which will kill the cmd.exe
process).

Or you could just double-click on the shortcut to the wu-enable.bat or
wu-disable.bat files, let the console window flicker by (opened for the
shell to run the batch file and then immediately closed when the batch
file ends) and run services.msc to see what happened to the state of the
BITS and WU services. I prefer this method to verify what happened
rather than relying on the stdout from the console commands (sc.exe)
which will only report a failure not what is the resultant state of the
services.