Printer Sharing Issues In latest windows

 In recent versions of Windows, sharing USB printers may be more challenging or not work as expected due to several reasons related to changes in how Windows handles device sharing, security settings, and networking. Here are some common factors that could explain this issue:

1. Changes in Network Printer Sharing Behavior

Windows 10 and later versions have evolved in terms of how they handle printer sharing, especially for USB printers. USB printers are typically directly connected to a single computer via USB, and sharing them over the network requires that the host machine (the one physically connected to the printer) be on and running.

In modern versions of Windows, there may be more restrictive rules for sharing USB printers, especially when connected to non-Home network types (e.g., Work or Public), which can make sharing more difficult.

2. Windows HomeGroup Deprecation

In earlier versions of Windows, the HomeGroup feature made sharing printers and files across devices in the same network easier. However, this feature was deprecated and removed starting with Windows 10 version 1803. The removal of HomeGroup may impact some of the simpler methods of printer sharing.

As a result, users may find that sharing USB printers now requires additional steps, such as manually setting up printer sharing or using modern sharing protocols.

3. USB Printer Redirection Over Network

USB printer sharing traditionally worked by redirecting USB devices over the network. In Windows 10 and later, the Windows Print Spooler and the related Print Management system have been updated, and there may be limitations or bugs related to sharing USB printers over the network.

Some third-party solutions that were used for USB redirection (like USB-over-IP software) may be necessary for reliable printer sharing across networks in newer versions of Windows.

4. Network and Security Settings

Network Isolation: Windows might treat devices on a different network as "untrusted," which can block printer sharing. This is particularly true when computers are connected to different types of networks (Private vs. Public).

Firewall and Security: Windows Defender and third-party firewalls are now more aggressive in blocking network sharing to prevent unauthorized access. You may need to modify the firewall settings or create specific rules to allow printer sharing.

Network Discovery: If "Network Discovery" is turned off, sharing a printer will not be possible. You must ensure that the printer's host computer has Network Discovery enabled in the Control Panel > Network and Sharing Center.

5. Driver Compatibility Issues

Some printer drivers are not fully compatible with newer versions of Windows or may require specific updates to support sharing over the network. Printer manufacturers may also release updates or patches to make their printers compatible with the latest version of Windows.

If you're having trouble with a specific printer model, it's worth checking the printer manufacturer's website for any updated drivers or utilities designed to improve network printing compatibility with newer Windows versions.

6. Sharing Configuration Changes

The process for setting up printer sharing may have changed slightly in recent versions of Windows. To share a USB printer:

• You need to go into Settings > Devices > Printers & Scanners, select the printer, and then choose Manage.
• Enable printer sharing by going to Control Panel > Devices and Printers, right-clicking on the printer, and selecting Printer Properties > Sharing.

However, it's possible that settings or options are different or hidden in some versions, making it harder to configure properly.

7. Windows Update Issues

Sometimes, Windows updates may introduce bugs or changes that break printer sharing functionality. If sharing was working previously and suddenly stopped, check whether there was a recent update that might have impacted printer sharing.

Potential Solutions:

• Enable Network Discovery: Make sure Network Discovery is turned on for the devices you want to share the printer with.
• Check Firewall Settings: Ensure that the necessary ports and sharing protocols (like SMB) are open on both the host and client machines.
• Update Printer Drivers: Install the latest drivers from the printer manufacturer’s website.
• Use a Workaround or Third-Party Software: Some third-party applications or tools, such as USB Network Gate or PrinterShare, can help with USB printer sharing over the network.

Automate Windows Apps Instalation

 

winget source update

winget install -e --id Google.Chrome --silent   

winget install -e --id VideoLAN.VLC --silent

winget install -e --id Mozilla.Firefox --silent

winget install -e --id RARLab.WinRAR --silent

winget install -e --id PowerSoftware.PowerISO --silent

winget install -e --id Easeware.DriverEasy --silent

winget search "driver easy"

snappy drivers

https://sdi-tool.org/download/

      

eSSL eTimeTrackLite Complete Tutorial Malayalam

Multiple RDP Sessions in Windows 10

 

Modifying Termsrv.dll File to Allow Multiple RDP Session

To remove the restriction on the number of concurrent RDP user connections in Windows 10 without using rdpwraper, you can replace the original termsrv.dll file. This is the library file used by the Remote Desktop Service. The file is located in C:\Windows\System32 directory.

Before you edit or replace the termsrv.dll file, it is advisable to create its backup copy. If necessary, this will help you to return to the original file version:

copy c:\Windows\System32\termsrv.dll termsrv.dll_backup

Before you edit the termsrv.dll file, you have to become its owner and give the Administrators group the full permissions to it. The easiest way to do this is from the command prompt. To change the file owner from TrustedInstaller to a local administrators group use the command:

akeown /F c:\Windows\System32\termsrv.dll /A

SUCCESS: The file (or folder): c:\Windows\System32\termsrv.dll now owned by the administrators group

Now grant the local administrators group Full Control permission on the termsrv.dll file:

icacls c:\Windows\System32\termsrv.dll /grant Administrators:F

processed file: c:\Windows\System32\termsrv.dll Successfully processed 1 files; Failed processing 0 files.

After that, stop the Remote Desktop service (TermService) from the services.msc console or from the command prompt:

Net stop TermService

Before moving on, you need to get your version (build number) of Windows 10. Open the PowerShell console and run the command:

Get-ComputerInfo | select WindowsProductName, WindowsVersionI have Windows 10 build 1909 installed on my computer.

Then open the termsrv.dll file using any HEX editor (for example, Tiny Hexer). Depending on your Windows 10 build, you need to find and replace the code according to the table below:

Windows 10 build	Find the string	Replace with
Windows 10 x64 1909	39 81 3C 06 00 00 0F 84 5D 61 01 00	B8 00 01 00 00 89 81 38 06 00 00 90
Windows 10 x64 1903	39 81 3C 06 00 00 0F 84 5D 61 01 00
Windows 10 x64 1809	39 81 3C 06 00 00 0F 84 3B 2B 01 00
Windows 10 x64 1803	8B 99 3C 06 00 00 8B B9 38 06 00 00
Windows 10 x64 1709	39 81 3C 06 00 00 0F 84 B1 7D 02 00

For example, for Windows 10 x64 RTM (10240) with the termsrv.dll file version 10.0.10240.16384, you need to find the line:

39 81 3C 06 00 00 0F 84 73 42 02 00

and replace it with:

B8 00 01 00 00 89 81 38 06 00 00 90

 

Save the file and run the TermService.

Already patched termsrv.dll file for Windows 10 Pro x64 can be downloaded here: termsrv_for_windows_10_x64_10240.zip

If something went wrong and you experience some problems with the Remote Desktop service, stop the service and replace the modified termsrv.dll file with the original version:

copy termsrv.dll_backup c:\Windows\System32\termsrv.dll

The advantage of the method of enabling multiple RDP sessions in Windows 10 by replacing the termsrv.dll file is that antiviruses do not respond on it (unlike the RDPWrap, which is detected by many antiviruses as a Malware/HackTool/Trojan).

The main drawback is that you will have to manually edit the termsrv.dll file each time you upgrade the Windows 10 build (or when updating the version of the termsrv.dll file during the installation of monthly cumulative updates).

Windows 10 x64 20H2 19042.746

After this update termsrv.dll is upgraded to version 10.0.19041.746 To get back concurrent remote desktop connections, make the following changes:

Find:

39 81 3C 06 00 00 0F 84 01 5E 01 00

replace with:

B8 00 01 00 00 89 81 38 06 00 00 90

What causes the ‘The Connection was Denied Because the User Account is not Authorized for Remote Login’ Error on Windows 10?

The cause of the error is in the error message itself that is —

• Insufficient permissions: The error pops up when your user account doesn’t have sufficient permissions to establish a connection with the target host.
• RD service: In some cases, the issue can also be if your Remote Desktop service has the wrong Log On user configured.

With that said, you can deal with the error by applying the following workarounds. Make sure to use an administrator account while implementing the given solutions.

Solution 1: Creating a New Security Group

In order to fix the issue, you might want to create a new security group whose members will have the power to establish a Remote Desktop connection. Here’s how to do it:

1. Press Windows Key + R to open Run.
2. Type in ‘secpol.msc’ and press Enter.
3. Navigate to Local Policies > User Rights Assignment.
4. From the list of policies, locate Allow log on through Remote Desktop Services and double-click it.Local Security Policy
5. If there’s no Remote Desktop Users group under Administrators, follow the below instructions. If you already have one, skip to the next solution.
6. Click Add User or Group and enter Remote Desktop Users under ‘Enter the object names to select’.Creating Remote Desktop Users Group
7. Hit OK.
8. Restart your system for it to take effect or you can just enter the following command in an elevated command prompt:gpupdate /force

Solution 2: Giving Access to your User Account

In some cases, if the user account that you are using to establish a Remote connection isn’t a member of the Remote Desktop Users group, you will be prompted with the said error. In such a scenario, you will have to add it in the Remote Desktop Users group. Here’s how to do that:

PRO TIP: If the issue is with your computer or a laptop/notebook you should try using Restoro Repair which can scan the repositories and replace corrupt and missing files. This works in most cases, where the issue is originated due to a system corruption. You can download Restoro by Clicking Here

1. Press Winkey + R to open Run.
2. Type in lusrmgr.msc and press Enter.
3. Click on Users and then double-click your user account.
4. Switch to the Member Of tab.User Groups
5. If there’s no Remote Desktop Users group under Administrators, click Add.
6. Select Advanced and then click Find now.
7. From the list, double-click Remote Desktop Users and then click OK.Adding User Account to Remote Desktop Users Group
8. Your user account is now a member of the Remote Desktop User group.
9. Try establishing a connection now.

Solution 3: Checking Remote Desktop Service Log On User

If your Remote Desktop Service is using Local Service instead of Network Service as the log on user, it can also cause the issue to occur. You can fix this by changing it to Network Service. Here’s how to do it:

1. Press Windows Key + R to open Run.
2. Type in ‘services.msc‘ and press Enter.
3. Locate Remote Desktop Service and then double-click it.Remote Desktop Service
4. Switch to the Log On tab.
5. If the Local Service account is selected, you’ll have to change it. Click Browse.
6. Select Advanced and then click Find now.
7. From the list, double-click Network Service and then click OK.Changing Remote Desktop Service Log On User
8. Restart the service by right-clicking the service and selecting Restart.

Sample works barcode

How to test barcode printer using  tets file

 SIZE 78.6 mm, 25 mm

GAP 3 mm, 0 mm

SPEED 2

DENSITY 7

DIRECTION 0,0

REFERENCE 0,0

OFFSET 0 mm

SHIFT 0

SET PEEL OFF

SET CUTTER OFF

SET PARTIAL_CUTTER OFF

SET TEAR ON

CLS

CODEPAGE 850

TEXT 595,191,"ROMAN.TTF",180,1,8,"ZOARA"

TEXT 271,191,"ROMAN.TTF",180,1,8,"ZOARA"

BARCODE 595,169,"128",44,0,180,2,4,"#bcode#"

TEXT 595,122,"ROMAN.TTF",180,1,8,"#bcodet#"

BARCODE 271,169,"128",44,0,180,2,4,"#bcode#"

TEXT 271,122,"ROMAN.TTF",180,1,8,"#bcodet#"

TEXT 459,120,"ROMAN.TTF",180,1,7,"MRP : #mrp#"

TEXT 135,120,"ROMAN.TTF",180,1,7,"MRP : #mrp#"

TEXT 595,100,"ROMAN.TTF",180,1,10,"Sale Rate : #srate#"

TEXT 271,100,"ROMAN.TTF",180,1,10,"Sale Rate : #srate#"

TEXT 595,73,"ROMAN.TTF",180,1,7,"#product#"

TEXT 271,73,"ROMAN.TTF",180,1,7,"#product#"

TEXT 595,29,"ROMAN.TTF",180,1,6,"CUSTOMER CARE NO : 8089235575"

TEXT 271,29,"ROMAN.TTF",180,1,6,"CUSTOMER CARE NO : 8089235575"

TEXT 443,42,"ROMAN.TTF",180,1,4,"Description : #Description#"

TEXT 119,42,"ROMAN.TTF",180,1,4,"Description : #Description#"

PRINT 2

CLS

God Mode

God Mode is a feature that provides a single location to access over 200 settings and tools in Windows. These tools can be used for everyday tasks like adding or removing apps, adjusting power settings, and creating System Restore points

Right-click on an empty space on your desktop, select New, and then Folder. Enter the folder name 

GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}.

Press Windows + R, type 

shell:::{ED7BA470-8E54-465E-825C-99712043E01C} 

in the Run dialog, and press Enter

Manual Edition changing Of Win 10/11

 

Manual Edition Change​

If you want to manually change the edition instead of using the script, please follow the steps below.

Windows 10/11​

• To view the list of available editions, open the command prompt as admin and enter
  dism /online /english /Get-TargetEditions
• Get the keys for the desired edition from here
• If you are upgrading from Home to Pro, you will need to disable the Internet before performing the upgrade.
• Now enter that product key with this command, replace <product_key> with the actual key.
  changepk.exe /ProductKey <product_key>
• In the Home to Pro upgrade, it may show an error, restart the system anyway. (Use the script if it's still not working)
• Activate the changed edition with MAS, that's all.